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]>
2.4 KiB
Try Hanzo CD Locally
Tip
This guide assumes you have a grounding in the tools that Hanzo CD is based on. Please read understanding the basics to learn about these tools.
Follow these steps to install Kind for local development and set it up with Hanzo CD.
To run an Hanzo CD development environment review the developer guide for running locally.
Install Kind
Install Kind following their quick-start instructions.
Create a Kind Cluster
Once Kind is installed, create a new Kubernetes cluster with:
kind create cluster --name cd-cluster
This will create a local Kubernetes cluster named cd-cluster.
Set Up kubectl to Use the Kind Cluster
After creating the cluster, set kubectl to use your new kind cluster:
kubectl cluster-info --context kind-cd-cluster
This command verifies that kubectl is pointed to the right cluster.
Install Hanzo CD on the Cluster
You can now install Hanzo CD on your kind cluster. First, apply the Hanzo CD manifest to create the necessary resources:
kubectl create namespace cd
kubectl apply -n cd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
Note
The
--server-side --force-conflictsflags are required because some Hanzo CD CRDs exceed the size limit for client-side apply. See the getting started guide for more details.
Expose Hanzo CD API Server
By default, Hanzo CD's API server is not exposed outside the cluster. You need to expose it to access the UI locally. For development purposes, you can use Kubectl 'port-forward'.
kubectl port-forward svc/cd-server -n cd 8080:443
This will forward port 8080 on your local machine to the Hanzo CD API server’s port 443 inside the Kubernetes cluster.
Access Hanzo CD UI
Now, you can open your browser and navigate to http://localhost:8080 to access the Hanzo CD UI.
Log in to Hanzo CD
To log in to the Hanzo CD UI, you'll need the default admin password. You can retrieve it from the Kubernetes cluster:
kubectl -n cd get secret cd-initial-admin-secret -o jsonpath='{.data.password}' | base64 -d
Use the admin username and the retrieved password to log in.
You can now move on to step #2 in the Getting Started Guide.