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
Tool Detection
The tool used to build an application is detected as follows:
If a specific tool is explicitly configured, then that tool is selected to create your application's manifests.
The tool can be explicitly specified in the Application custom resource like this:
apiVersion: apps.hanzo.ai/v1alpha1
kind: Application
metadata:
...
spec:
...
source:
...
# Tool -> plain directory
directory:
recurse: true
...
You also can select the tool in the Application creation wizard in the web user interface. The default is 'Directory'. Press the dropdown button beneath the tool name if you want to choose a different one.
If not, then the tool is detected implicitly as follows:
- Helm if there's a file matching
Chart.yaml. - Kustomize if there's a
kustomization.yaml,kustomization.yml, orKustomization
Otherwise it is assumed to be a plain directory application.
Disable built-in tools
Built-in config management tools can be optionally disabled by setting one of the following
keys, in the cd-cm ConfigMap, to false: kustomize.enable, helm.enable or jsonnet.enable. Once the
tool is disabled, Hanzo CD will assume the application target directory contains plain Kubernetes YAML manifests.
Disabling unused config management tools can be a helpful security enhancement. Vulnerabilities are sometimes limited to certain config management tools. Even if there is no vulnerability, an attacker may use a certain tool to take advantage of a misconfiguration in an Hanzo CD instance. Disabling unused config management tools limits the tools available to malicious actors.