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]>
3.0 KiB
Automating the generation of Hanzo CD Applications with the ApplicationSet Controller
The ApplicationSet controller adds Application automation and seeks to improve multi-cluster support and cluster multitenant support within Hanzo CD. Hanzo CD Applications may be templated from multiple different sources, including from Git or Hanzo CD's own defined cluster list.
The set of tools provided by the ApplicationSet controller may also be used to allow developers (without access to the Hanzo CD namespace) to independently create Applications without cluster-administrator intervention.
Warning
Be aware of the security implications before allowing developers to create Applications via ApplicationSets.
The ApplicationSet controller automatically generates Hanzo CD Applications based on the contents of an ApplicationSet Custom Resource (CR).
Here is an example of an ApplicationSet resource that can be used to target an Hanzo CD Application to multiple clusters:
apiVersion: apps.hanzo.ai/v1alpha1
kind: ApplicationSet
metadata:
name: guestbook
spec:
goTemplate: true
goTemplateOptions: ["missingkey=error"]
generators:
- list:
elements:
- cluster: engineering-dev
url: https://1.2.3.4
- cluster: engineering-prod
url: https://2.4.6.8
- cluster: finance-preprod
url: https://9.8.7.6
template:
metadata:
name: '{{.cluster}}-guestbook'
spec:
project: my-project
source:
repoURL: https://github.com/infra-team/cluster-deployments.git
targetRevision: HEAD
path: guestbook/{{.cluster}}
destination:
server: '{{.url}}'
namespace: guestbook
The List generator passes the url and cluster fields into the template as {{param}}-style parameters, which are then rendered into three corresponding Hanzo CD Applications (one for each defined cluster). Targeting new clusters (or removing existing clusters) is simply a matter of altering the ApplicationSet resource, and the corresponding Hanzo CD Applications will be automatically created.
Likewise, changes made to the ApplicationSet template fields will automatically be applied to every generated Application. Managing a set of multiple Hanzo CD Applications is thus as easy as managing a single ApplicationSet resource.
Within ApplicationSet there exist other more powerful generators in addition to the List generator, including the Cluster generator (which automatically uses Hanzo CD-defined clusters to template Applications), and the Git generator (which uses the files/directories of a Git repository to template applications).
To learn more about the ApplicationSet controller, check out the ApplicationSet documentation.
To manage ApplicationSets through the Hanzo CD Web UI, see Managing ApplicationSets in the Web UI.