Files
universe/deploy/lux-bridge/kv.yaml
T
zeekayandHanzo Dev 425b96f66e the cluster is named, not addressed by a gone account
Every provenance line and manifest still named a DigitalOcean context, and
the ARC values described a pool that died with it. A cluster gets a name
here; the address it answers on belongs to the private record.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 16:15:33 -07:00

49 lines
1.2 KiB
YAML

# Generated from the live lux-bridge/kv Deployment on lux-k8s
# by hack/live2values.py. Live is the source: a repo of hand-applied
# manifests has unknown currency, the running fleet does not.
replicas: 1
selectorLabels:
app: kv
image:
repository: ghcr.io/hanzoai/kv
tag: '9'
pullPolicy: Always
resources: {}
volumeMounts:
- mountPath: /data
name: kv-storage
livenessProbe:
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 10
successThreshold: 1
tcpSocket:
port: 6379
timeoutSeconds: 1
readinessProbe:
failureThreshold: 3
initialDelaySeconds: 5
periodSeconds: 5
successThreshold: 1
tcpSocket:
port: 6379
timeoutSeconds: 1
ports:
- containerPort: 6379
name: redis
volumes:
- name: kv-storage
persistentVolumeClaim:
claimName: kv-pvc
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
imagePullSecrets: []
# RWO volume + one replica: Recreate, not RollingUpdate. A rolling update
# guarantees an overlap, the new pod cannot attach a ReadWriteOnce volume the
# old one holds, and the rollout parks on Multi-Attach forever while the old
# pod keeps serving — measured on status and elastic. Recreate costs one
# bounded restart and completes.
strategy: Recreate