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.5 KiB
External URL Links
Hanzo CD automatically generates clickable links to external pages that your application exposes.
This is usually done via detecting hosts / URLs from your Ingress resources.
Add external URL
You can add additional external links to Hanzo CD dashboard. For example links to monitoring pages or documentation, instead of just ingress hosts or other apps.
Hanzo CD generates clickable links to external pages for a resource based on per resource annotation.
Example:
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-svc
annotations:
link.cd.hanzo.ai/external-link: http://my-grafana.example.com/pre-generated-link
The external link icon will be visible for respective resource on Hanzo CD application details page.
Ignore autogenerated external URLs
If an ingress object should be ignored by Hanzo CD's autodetection of external URLs, such as a dummy ingress
pointing to a 404 page, you can add the cd.hanzo.ai/ignore-default-links: "true" annotation. This will
remove any links inferred from the ingress spec from the Hanzo CD UI. Any links added by link.cd.hanzo.ai
annotations are unchanged.
Example:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
annotations:
link.cd.hanzo.ai/external-link: https://optional.show-me-instead.example.com/
cd.hanzo.ai/ignore-default-links: "true"
spec:
rules:
- host: dont-show-me.internal.example.com
...