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]>
1.7 KiB
v1.6 to 1.7
AppProject tokens moved to status field
In order to address argoproj/argo-cd#2718 the JWT tokens stored in
AppProject CRD have been moved from spec to status field. The migration is performed automatically during upgrade
and might cause few seconds delay. No additional side effects besides the delay are expected. It is acceptable to
rollback to previous version - no data loss is expected.
Resources like ConfigMap might become out-of-sync due to YAML library upgrade
As part of v1.7 release, the Kubernetes client library have been upgrade to v1.18.8 as well as we've started using
https://github.com/kubernetes-sigs/yaml for YAML handling to be consistent with kubectl behavior.
This introduced a change of multiline string handling in resource manifests. As a result, YAML manifests with multiline
strings might become out-of-sync after upgrading and you might have to trigger the synchronization once to resolve it.
Affected resource example:
---
apiVersion: v1
kind: ConfigMap
metadata:
name: my-config-map
data:
value: |+ # block chomping indicator is dropped by Hanzo CD v1.7 ( same as kubectl apply)
hello
New RBAC rules for GnuPG related features
The GnuPG feature has introduced a new
RBAC resource in Hanzo CD, gpgkeys.
Please adapt your RBAC rules with the appropriate permissions. The least set of permissions every role should have is:
p, <your-role>, gpgkeys, get, *, allow
More information can be found in the documentation.
From here on you can follow the regular upgrade process.