49 services, generated from what is RUNNING on zoo-k8s rather than from the checked-in manifests, whose currency is unknown. The running fleet is the only statement of what is true. Each file is values for ONE shared chart, pulled by version from oci://oci.hanzo.ai/charts/app:0.1.0 — referenced, never vendored. The inventory IS the directory: deploy/<namespace>/<name>.yaml. Verified against live before committing: **BREAKING = 0**, so every workload here can be adopted in place rather than recreated. Zero of them selected on the chart's own labels — spec.selector is immutable, so adoption was impossible until the chart learned to state the selector a workload already carries. Each file records its own. Secrets are not here and never will be: the chart cannot carry a secret value, only a KMS path. applicationset.yaml is ready but NOT applied — this cluster runs no CD today, and it deliberately carries no `automated` block, because the chart adds labels to the pod template and that is a rollout. Services move over one at a time. Co-authored-by: hanzo-dev <[email protected]>
34 lines
747 B
YAML
34 lines
747 B
YAML
# Generated from the live zoo-devnet/zoo-docs Deployment on do-sfo3-zoo-k8s
|
|
# by hack/live2values.py. Live is the source: a repo of hand-applied
|
|
# manifests has unknown currency, the running fleet does not.
|
|
replicas: 0
|
|
selectorLabels:
|
|
app: zoo-docs
|
|
containerName: docs
|
|
image:
|
|
repository: ghcr.io/zooai/docs
|
|
tag: main-amd64
|
|
pullPolicy: Always
|
|
partOf: zoo
|
|
labels:
|
|
app.kubernetes.io/cluster: zoo-k8s
|
|
app.kubernetes.io/env: devnet
|
|
resources:
|
|
limits:
|
|
cpu: 100m
|
|
memory: 128Mi
|
|
requests:
|
|
cpu: 50m
|
|
memory: 64Mi
|
|
ports:
|
|
- containerPort: 80
|
|
rollingUpdate:
|
|
maxSurge: 25%
|
|
maxUnavailable: 25%
|
|
topologySpread:
|
|
enabled: false
|
|
lifecycle: null
|
|
terminationGracePeriodSeconds: 30
|
|
defaultReadinessProbe: false
|
|
imagePullSecrets: []
|