mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00

Files

T

zeekayandHanzo Dev 446e343a3d cd: annotations are cd.hanzo.ai, API group is apps.hanzo.ai

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]>

2026-07-28 16:32:14 -07:00

5.4 KiB

Raw Permalink Blame History

Getting Started

This guide assumes you are familiar with Hanzo CD and its basic concepts. See the Hanzo CD documentation for more information.

Requirements

Installed kubectl command-line tool
Have a kubeconfig file (default location is ~/.kube/config).

Installation

There are a few options for installing the ApplicationSet controller.

A) Install ApplicationSet as part of Hanzo CD

Starting with Hanzo CD v2.3, the ApplicationSet controller is bundled with Hanzo CD. It is no longer necessary to install the ApplicationSet controller separately from Hanzo CD.

Follow the Hanzo CD Getting Started instructions for more information.

B) Install ApplicationSet into an existing Hanzo CD install (pre-Hanzo CD v2.3)

Note: These instructions only apply to versions of Hanzo CD before v2.3.0.

The ApplicationSet controller must be installed into the same namespace as the Hanzo CD it is targeting.

Presuming that Hanzo CD is installed into the cd namespace, run the following command:

kubectl apply -n cd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/applicationset/v0.4.0/manifests/install.yaml

Once installed, the ApplicationSet controller requires no additional setup.

The manifests/install.yaml file contains the Kubernetes manifests required to install the ApplicationSet controller:

CustomResourceDefinition for ApplicationSet resource
Deployment for cd-applicationset-controller
ServiceAccount for use by ApplicationSet controller, to access Hanzo CD resources
Role granting RBAC access to needed resources, for ServiceAccount
RoleBinding to bind the ServiceAccount and Role

Enabling high availability mode

To enable high availability, you have to set the command --enable-leader-election=true in cd-applicationset-controller container and increase the replicas.

do following changes in manifests/install.yaml

    spec:
      containers:
      - command:
        - entrypoint.sh
        - cd-applicationset-controller
        - --enable-leader-election=true

Optional: Additional Post-Upgrade Safeguards

See the Controlling Resource Modification page for information on additional parameters you may wish to add to the ApplicationSet Resource in install.yaml, to provide extra security against any initial, unexpected post-upgrade behaviour.

For instance, to temporarily prevent the upgraded ApplicationSet controller from making any changes, you could:

Enable dry-run
Use a create-only policy
Enable preserveResourcesOnDeletion on your ApplicationSets
Temporarily disable automated sync in your ApplicationSets' template

These parameters would allow you to observe/control the behaviour of the new version of the ApplicationSet controller in your environment, to ensure you are happy with the result (see the ApplicationSet log file for details). Just don't forget to remove any temporary changes when you are done testing!

However, as mentioned above, these steps are not strictly necessary: upgrading the ApplicationSet controller should be a minimally invasive process, and these are only suggested as an optional precaution for extra safety.

Next Steps

Once your ApplicationSet controller is up and running, proceed to Use Cases to learn more about the supported scenarios, or proceed directly to Generators to see example ApplicationSet resources.

5.4 KiB Raw Permalink Blame History