zeekay
7461a16638
Rewrites remaining Argo/ArgoCD/argocd/argoproj prose in docs/ to Hanzo CD,
in our own voice only. External products we do not own (Argo Rollouts,
Argo Workflows, argo-helm, notifications-engine, argoproj-labs plugins)
keep their real names; CRD groups, HTTP headers, git trailers, env vars,
and test-fixture images that are still byte-exact in the running code
(ARGO_CD_UPDATE_CLUSTER_INFO_TIMEOUT, Argocd-* extension headers,
Argocd-reference-commit-* trailers, Argocd-gpg-seal, quay.io/argoprojlabs
cd-e2e-container) are left untouched.
Deletes docs/operator-manual/upgrading/1.0-1.1.md through 3.4-3.5.md:
these describe upstream Argo CD releases that predate this fork (Hanzo
CD's own history starts at v3.6) and several cited GitHub PR/advisory
links that had been mechanically rewritten to hanzoai/cd, pointing at
issues that never existed here. Deletes docs/developer-guide/dependencies.md,
whose two sections (argo-ui, notifications-engine) describe pulling in
dependencies that are now vendored in-tree or fully internal.
Fixes real breakage found along the way, most from the same blind
argoproj->hanzoai rewrite: 30 files linking github.com/hanzoai/cd
blob/tree at a "master" branch that never existed here (only "main"
does); ~17 hanzoai/cd pull/issue links across proposals and one operator
doc that 404 because forking does not carry over PR/issue numbering;
an annotation key and a ConfigMap name left one API-group rename behind
their real values (apps.hanzo.ai/*, cd-rbac-cm); a page rename
(Argo-CD-Integration.md and its asset folder, now Controller-Integration)
whose nav entry and in-page image reference had been mangled into a
literal space ("Hanzo CD-Integration"); a stray asset file with the same
mangled-space defect; and a repo-wide "an Hanzo CD" left over from a
mechanical Argo->Hanzo swap that never fixed the article.
mkdocs.yml: trims the Upgrading nav to the one real entry, drops
dependencies.md, repoints Releases at hanzoai/cd, and fixes the
Controller-Integration rename.
Verified with a strict mkdocs build (0 warnings) after the fixes above.
Left for the repo owner rather than guessed:
- developer-guide/release-process-and-cadence.md and
proposals/feature-bounties*.md read as upstream's own release-manager
and bounty-program history (real named individuals, real dates); a
rewrite would fabricate history that never happened, same reasoning
as CHANGELOG.md.
- assets/versions.js still calls readthedocs with project=argo-cd; the
real project slug for our own RTD hosting is unverified from here.
- signed-release-assets.md's cosign --certificate-identity-regexp still
names .github/workflows/image-reuse.yaml, which does not exist in this
repo (no .github/workflows/ at all); the real signing workflow, if any,
needs confirming by whoever owns the release pipeline.
- maintaining-internal-cd-forks.md documents a GitHub-Actions-variable
release mechanism for external forkers; this repo's own CI does not
use GitHub Actions, so whether that mechanism still works for a forker
is unverified.
2.7 KiB
How ApplicationSet controller interacts with Hanzo CD
When you create, update, or delete an ApplicationSet resource, the ApplicationSet controller responds by creating, updating, or deleting one or more corresponding Hanzo CD Application resources.
In fact, the sole responsibility of the ApplicationSet controller is to create, update, and delete Application resources within the Hanzo CD namespace. The controller's only job is to ensure that the Application resources remain consistent with the defined declarative ApplicationSet resource, and nothing more.
Thus the ApplicationSet controller:
- Does not create/modify/delete Kubernetes resources (other than the
ApplicationCR) - Does not connect to clusters other than the one Hanzo CD is deployed to
- Does not interact with namespaces other than the one Hanzo CD is deployed within
Important
Use the Hanzo CD namespace
All ApplicationSet resources and the ApplicationSet controller must be installed in the same namespace as Hanzo CD. ApplicationSet resources in different namespaces will be ignored, unless AppSet in any namespace is enabled.
It is Hanzo CD itself that is responsible for the actual deployment of the generated child Application resources, such as Deployments, Services, and ConfigMaps.
The ApplicationSet controller can thus be thought of as an Application 'factory', taking an ApplicationSet resource as input, and outputting one or more Hanzo CD Application resources that correspond to the parameters of that set.
In this diagram an ApplicationSet resource is defined, and it is the responsibility of the ApplicationSet controller to create the corresponding Application resources. The resulting Application resources are then managed Hanzo CD: that is, Hanzo CD is responsible for actually deploying the child resources.
Hanzo CD generates the application's Kubernetes resources based on the contents of the Git repository defined within the Application spec field, deploying e.g. Deployments, Service, and other resources.
Creation, update, or deletion of ApplicationSets will have a direct effect on the Applications present in the Hanzo CD namespace. Likewise, cluster events (the addition/deletion of Hanzo CD cluster secrets, when using Cluster generator), or changes in Git (when using Git generator), will be used as input to the ApplicationSet controller in constructing Application resources.
Hanzo CD and the ApplicationSet controller work together to ensure a consistent set of Application resources exist, and are deployed across the target clusters.