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.2 KiB
UI Customization
Default Application Details View
By default, the Application Details will show the Tree view.
This can be configured on an Application basis, by setting the pref.cd.hanzo.ai/default-view annotation, accepting one of: tree, pods, network, list as values.
For the Pods view, the default grouping mechanism can be configured using the pref.cd.hanzo.ai/default-pod-sort annotation, accepting one of: node, parentResource, topLevelResource as values.
Node Labels in Pod View
It's possible to propagate node labels to node information in the pod view by configuring application.allowedNodeLabels in the cd-cm ConfigMap.
The following configuration:
application.allowedNodeLabels: topology.kubernetes.io/zone,karpenter.sh/capacity-type
Would result in:
CLI Download Links
The Help page (linked from the bottom of the sidebar) always shows a download button for the Linux CLI binary that is embedded in the Hanzo CD server, so users can fetch a working CLI without any configuration.
To offer the CLI for additional operating systems and architectures, set help.download.<os>-<arch> keys in the cd-cm ConfigMap. Each configured key adds a download button on the Help page pointing at the URL you provide:
apiVersion: v1
kind: ConfigMap
metadata:
name: cd-cm
namespace: cd
data:
help.download.linux-amd64: "https://example.com/cd-linux-amd64"
help.download.linux-arm64: "https://example.com/cd-linux-arm64"
help.download.darwin-amd64: "https://example.com/cd-darwin-amd64"
help.download.darwin-arm64: "https://example.com/cd-darwin-arm64"
help.download.windows-amd64: "https://example.com/cd-windows-amd64.exe"
The following <os>-<arch> keys are recognized; any other key is ignored:
linux-amd64linux-arm64linux-ppc64lelinux-s390xdarwin-amd64darwin-arm64windows-amd64
Note
The default Linux button is always shown in addition to any configured links, so configuring
help.download.linux-<arch>for the server's own architecture results in two Linux buttons.