Files
universe/deploy/lux-devnet/kms-zap-operator.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

43 lines
961 B
YAML

# Generated from the live lux-devnet/kms-zap-operator 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: 0
selectorLabels:
app: kms-zap-operator
containerName: operator
image:
repository: ghcr.io/luxfi/kms-operator
tag: v1.11.7
pullPolicy: IfNotPresent
env:
- name: WATCH_NAMESPACE
value: lux-devnet
- name: RESYNC_INTERVAL
value: '30'
- name: ZAP_PORT
value: '9999'
resources: {}
livenessProbe:
failureThreshold: 3
httpGet:
path: /healthz
port: 8080
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
ports:
- containerPort: 8080
imagePullSecrets:
- name: ghcr-luxfi
serviceAccountName: kms-zap-operator
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
defaultReadinessProbe: false