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.6 KiB
Cluster Management
This guide is for operators looking to manage clusters on the CLI. If you want to use Kubernetes resources for this, check out Declarative Setup.
Not all commands are described here, see the cd cluster Command Reference for all available commands.
Adding a cluster
Run cd cluster add context-name.
If you're unsure about the context names, run kubectl config get-contexts to get them all listed.
This will connect to the cluster and install the necessary resources for Hanzo CD to connect to it. Note that you will need privileged access to the cluster.
Skipping cluster reconciliation
You can stop the controller from reconciling a cluster without removing it by annotating its secret:
kubectl -n cd annotate secret <cluster-secret-name> cd.hanzo.ai/skip-reconcile=true
The cluster will still appear in cd cluster list but the controller will skip reconciliation
for all apps targeting it. To resume, remove the annotation:
kubectl -n cd annotate secret <cluster-secret-name> cd.hanzo.ai/skip-reconcile-
See Declarative Setup - Skipping Cluster Reconciliation for details.
Removing a cluster
Run cd cluster rm context-name.
This removes the cluster with the specified name.
Note
in-cluster cannot be removed
The
in-clustercluster cannot be removed with this. If you want to disable thein-clusterconfiguration, you need to update yourcd-cmConfigMap. Setcluster.inClusterEnabledto"false"