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]>
The fork was already ours everywhere that matters — our image, our IAM (dex
is not deployed), hanzo kv behind what the env still called REDIS. Only the
vocabulary was upstream's: ARGOCD_* across the Go, the manifests, the docs
and the plugin contract, and mkdocs still titled 'Argo CD' pointing at
argoproj/argo-cd.
ARGOCD_ -> CD_ and REDIS_ -> KV_ across 345 files, plus the 8 e2e/cmp
fixtures that assert the plugin env contract — those had to move with the
binary, which now emits CD_APP_NAME where they expected ARGOCD_APP_NAME.
Left alone deliberately, because renaming them would be wrong:
- util/helm/testdata/redis/ and gitops-engine/.../statefulset*.yaml are
fixtures for a THIRD-PARTY chart named redis, not our config
- util/kustomize/testdata/ likewise
- generated.proto regenerates from types.go, which is already clean
go build ./... exit 0.
LOCKSTEP: the live StatefulSet sets 47 ARGOCD_* names the binary no longer
reads. universe 4a5375735 carries the matching manifest change; they deploy
together or the controller falls back to defaults.
Co-authored-by: Hanzo Dev <[email protected]>
This PR adds some sentences to explain the process of "Syncing via UI" screenshots to have a good understanding of the process on the UI.
Signed-off-by: Rodolfo Martínez Vega <[email protected]>
* docs: remove core install commands from getting started
I often accidentally run the core install commands when quickly copying and pasting commands from the getting started guide, which leads to confusion. I've also spent plenty of time helping newcomers to Argo CD who have done the same and are confused when they can't reach the UI.
Given that this is a "getting started" guide, it's ideal to provide only the commands required. I've removed the commands and left the link out to the core install page for those who are interested in going down that path.
Signed-off-by: Nicholas Morey <[email protected]>
* fix: use link to install commands in core docs
Signed-off-by: Nicholas Morey <[email protected]>
* fix: use tip and improve wording
Signed-off-by: Nicholas Morey <[email protected]>
---------
Signed-off-by: Nicholas Morey <[email protected]>
* Fix#9429: A couple of notes in the docs to explain that the default certificate is insecure.
Signed-off-by: Jim Talbut <[email protected]>
* Fixes#9429: More verbose, but complete, text for Getting Started.
Signed-off-by: Jim Talbut <[email protected]>
Add echo to the end of the kubectl command to fetch initial admin secrets so that '%' new line character is not printed at the end of the secret.
Signed-off-by: mustafa89 <[email protected]>
Co-authored-by: Mustafa Mujahid <[email protected]>
The instructions for telling the CLI how to automatically use
port-forward were intertwined with the instructions for registering a
repo; this separates them.
This also moves the port-forward flags instructions to the first place
in the doc a user would need them.
Signed-off-by: Josh Gavant <[email protected]>
* fix: Generate initial admin password in a more secure manner
Signed-off-by: jannfis <[email protected]>
* Make CreateOrUpdateSecret method public
Signed-off-by: jannfis <[email protected]>
zeekayandHanzo Dev