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]>
36 lines
814 B
YAML
36 lines
814 B
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: nested-test-deployment
|
|
namespace: default
|
|
labels:
|
|
app: nested-test
|
|
applications.apps.hanzo.ai/app-name: nested-app
|
|
spec:
|
|
replicas: 1
|
|
selector:
|
|
matchLabels:
|
|
app: nested-test
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: nested-test
|
|
spec:
|
|
automountServiceAccountToken: false
|
|
containers:
|
|
- name: main-container
|
|
image: 'nginx:latest'
|
|
ports:
|
|
- containerPort: 80
|
|
name: http
|
|
protocol: TCP
|
|
- containerPort: 443
|
|
name: https
|
|
env:
|
|
- name: ENV_VAR1
|
|
value: "value1"
|
|
- name: ENV_VAR2
|
|
value: "value2"
|
|
resources:
|
|
limits:
|
|
memory: 100Mi |