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.3 KiB
The Hanzo CD UI displays icons for various Kubernetes resource types to help users quickly identify them. Hanzo CD includes a set of built-in icons for common resource types.
You can contribute additional icons for custom resource types by following these steps:
- Ensure the license is compatible with Apache 2.0.
- Add the icon file to the
ui/src/assets/images/resources/<group>/icon.svgpath in the Hanzo CD repository. - Modify the SVG to use the correct color,
#8fa4b1. - Run
make resourceiconsgento update the generated typescript file that lists all available icons. - Create a pull request to the Hanzo CD repository with your changes.
<group> is the API group of the custom resource. For example, if you are adding an icon for a custom resource with the
API group example.com, you would place the icon at ui/src/assets/images/resources/example.com/icon.svg.
If you want the same icon to apply to resources in multiple API groups with the same suffix, you can create a directory
prefixed with an underscore. The underscore will be interpreted as a wildcard. For example, to apply the same icon to
resources in the example.com and another.example.com API groups, you would place the icon at
ui/src/assets/images/resources/_.example.com/icon.svg.