Files
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

61 lines
1.3 KiB
YAML

# Generated from the live lux-mpc/mpc-dashboard 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: mpc-dashboard
containerName: dashboard
image:
repository: ghcr.io/luxfi/mpc-dashboard
digest: sha256:ac9397abc3a290a0137a1db1d155b2ef6a31193eb0ff6844c63b269b24be645a
pullPolicy: Always
partOf: lux-mpc
env:
- name: NEXT_PUBLIC_API_URL
value: https://mpc.lux.cloud/api/v1
- name: NEXT_PUBLIC_IAM_URL
value: https://lux.id
- name: NEXT_PUBLIC_IAM_CLIENT_ID
value: lux-mpc
- name: HOSTNAME
value: 0.0.0.0
resources:
limits:
cpu: 200m
memory: 256Mi
requests:
cpu: 50m
memory: 128Mi
livenessProbe:
failureThreshold: 3
httpGet:
path: /
port: 3000
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 30
successThreshold: 1
timeoutSeconds: 5
readinessProbe:
failureThreshold: 3
httpGet:
path: /
port: 3000
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5
ports:
- containerPort: 3000
name: http
imagePullSecrets:
- name: registry-hanzo
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30