mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
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]>
32 lines
1.0 KiB
YAML
32 lines
1.0 KiB
YAML
apiVersion: policy/v1
|
|
kind: PodDisruptionBudget
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/tracking-id: 'myapp:policy/PodDisruptionBudget:default/myapp-pdb'
|
|
kubectl.kubernetes.io/last-applied-configuration: >
|
|
{"apiVersion":"policy/v1","kind":"PodDisruptionBudget","metadata":{"annotations":{"cd.hanzo.ai/tracking-id":"myapp:policy/PodDisruptionBudget:default/myapp-pdb"},"name":"myapp-pdb","namespace":"default"},"spec":{"minAvailable":1,"selector":{"matchLabels":{"app":"myapp","version":"v1"}}}}
|
|
creationTimestamp: '2024-01-10T10:00:00Z'
|
|
generation: 1
|
|
name: myapp-pdb
|
|
namespace: default
|
|
resourceVersion: '12345'
|
|
uid: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
|
|
spec:
|
|
minAvailable: 1
|
|
selector:
|
|
matchLabels:
|
|
app: myapp
|
|
version: v1
|
|
status:
|
|
conditions:
|
|
- lastTransitionTime: '2024-01-10T10:00:00Z'
|
|
message: ''
|
|
reason: SufficientPods
|
|
status: 'True'
|
|
type: DisruptionAllowed
|
|
currentHealthy: 3
|
|
desiredHealthy: 1
|
|
disruptionsAllowed: 2
|
|
expectedPods: 3
|
|
observedGeneration: 1
|