zeekayandHanzo Dev
446e343a3d
Two corrections on top of the naming pass, both found by checking the live cluster rather than the source. The rename had silently changed the user-facing annotation key from argocd.argoproj.io/sync-wave to cd.argoproj.io/sync-wave — 63 live Applications carry the old key, so deploying that would have ignored every sync-wave and broken fleet deploy ordering. The key is now cd.hanzo.ai/*, and universe 575650286 moves the ApplicationSet template that stamps it, so the controller regenerates all 63 consistently. The API group in code said argoproj.io/v1alpha1 in 157 places while the cluster has served apps.hanzo.ai/v1alpha1 since 2026-07-23 (the CRDs are applications.apps.hanzo.ai). Code now matches what is actually served. The legacy applications.argoproj.io/app-name label had ZERO live users, so it went with the rest. foo.argoproj.io test fixtures became foo.example.com — arbitrary test domains should not carry a vendor name. go build ./... exit 0. Co-authored-by: Hanzo Dev <[email protected]>
3.2 KiB
v2.7 to 2.8
Support dropped for cd-cm plugins
Config Management Plugins installed via the cd-cm ConfigMap will not work starting with v2.8.
See the migration guide to upgrade your plugin.
Tini as entrypoint
With the 2.8 release entrypoint.sh will be removed from the containers,
because starting with 2.7, the implicit entrypoint is set to tini in the
Dockerfile explicitly, and the Kubernetes manifests has been updated to use
it. Simply updating the containers without updating the deployment manifests
will result in pod startup failures, as the old manifests are relying on
entrypoint.sh instead of tini. Please make sure the manifests are updated
properly before moving to 2.8.
Filtering applied to cluster List API endpoint
Prior to v2.8, the List endpoint on the ClusterService did not filter
clusters when responding, despite accepting query parameters. This bug has
been addressed, and query parameters are now taken into account to filter the
resulting list of clusters.
Configure RBAC to account for new actions
2.8 introduces three new actions:
- Create a Job from a CronJob
- Create a Workflow from a CronWorkflow
- Create a Workflow from a WorkflowTemplate
When you upgrade to 2.8, RBAC policies with applications in the resource
field and * or action/* in the action field, it will automatically grant the
ability to use these new actions.
If you would like to avoid granting these new permissions, you can update your RBAC policies to be more specific.
Example
Old:
p, role:action-runner, applications, actions/, *, allow
New:
p, role:action-runner, applications, action/apps.hanzo.ai/Rollout/abort, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/Rollout/promote-full, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/Rollout/retry, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/Rollout/resume, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/Rollout/restart, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/AnalysisRun/terminate, *, allow
p, role:action-runner, applications, action/apps/DaemonSet/restart, *, allow
p, role:action-runner, applications, action/apps/StatefulSet/restart, *, allow
p, role:action-runner, applications, action/apps/Deployment/pause, *, allow
p, role:action-runner, applications, action/apps/Deployment/resume, *, allow
p, role:action-runner, applications, action/apps/Deployment/restart, *, allow
# If you don't want to grant the new permissions, don't include the following lines
p, role:action-runner, applications, action/apps.hanzo.ai/WorkflowTemplate/create-workflow, *, allow
p, role:action-runner, applications, action/apps.hanzo.ai/CronWorkflow/create-workflow, *, allow
p, role:action-runner, applications, action/batch/CronJob/create-job, *, allow
Change default file open mode
In version 2.7, the CMP plugin was changed to open Git/Helm files with all executable bits set (unless preserveFileMode was specified).
Version 2.8 removes the executable bits in cases where they are not necessary.