mirror of
https://github.com/hanzoai/deploy.git
synced 2026-10-07 08:44:50 +00:00
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]>
35 lines
893 B
YAML
35 lines
893 B
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
annotations:
|
|
cd.hanzo.ai/tracking-id: 'guestbook:apps/Deployment:default/kustomize-guestbook-ui'
|
|
iksm-version: '1.0'
|
|
name: kustomize-guestbook-ui
|
|
namespace: default
|
|
spec:
|
|
replicas: 1
|
|
revisionHistoryLimit: 3
|
|
selector:
|
|
matchLabels:
|
|
app: guestbook-ui
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: guestbook-ui
|
|
spec:
|
|
containers:
|
|
- env:
|
|
- name: SOME_OTHER_ENV_VAR
|
|
value: some_other_value
|
|
- name: YET_ANOTHER_ENV_VAR
|
|
value: yet_another_value
|
|
- name: SOME_ENV_VAR
|
|
value: different_value!
|
|
image: 'quay.io/argoprojlabs/cd-e2e-container:0.1'
|
|
name: guestbook-ui
|
|
ports:
|
|
- containerPort: 80
|
|
resources:
|
|
requests:
|
|
cpu: 50m
|
|
memory: 100Mi |