hanzoai/deploy
2
0
Fork 0
mirror of https://github.com/hanzoai/deploy.git synced 2026-10-07 08:44:50 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
deploy/docs/user-guide/scale_application_resources.md
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

1.3 KiB
Raw Permalink Blame History

Scale Resources in Hanzo CD UI

This enables users to scale resources directly from the Hanzo CD UI. Users will be able to increase or decrease the number of replicas (Pods) for Deployments and StatefulSets by using an input field. The feature aims to enhance user experience, especially for non-technical users, by eliminating the need to modify configuration files or use kubectl commands for scaling.

Example Usage

  1. User navigates to a Deployment or StatefulSet in any Hanzo CD application.
  2. User clicks on the Actions dropdown and selects "Scale". action button for scaling
  3. A modal pops up showing an input field Enter input parameters for action: scale with the current number of Pods.
  4. User adjusts the number of Pods by entering a number. input field for scaling
  5. User presses OK, and the resource is scaled accordingly. result for scaling

Note

This feature will only apply to Deployments, and StatefulSets.

Note

If you use HPA (Horizontal Pod Autoscaling) or enabled Hanzo CD auto-sync, changing the replica count in scale actions would be overwritten. Ensure that invalid values (e.g., non-numeric characters, negative numbers, or values beyond the max integer limit) cannot be entered.

Reference in New Issue View Git Blame Copy Permalink