Files
universe/deploy/lux-ns/lux-market.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

66 lines
1.6 KiB
YAML

# Generated from the live lux-ns/lux-market 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: lux-market
containerName: market
image:
repository: ghcr.io/luxfi/lux-market
tag: v2.0.0
pullPolicy: Always
env:
- name: NODE_ENV
value: production
- name: NEXT_TELEMETRY_DISABLED
value: '1'
resources:
limits:
cpu: 500m
memory: 512Mi
requests:
cpu: 100m
memory: 256Mi
livenessProbe:
failureThreshold: 3
httpGet:
path: /
port: 3000
scheme: HTTP
initialDelaySeconds: 10
periodSeconds: 30
successThreshold: 1
timeoutSeconds: 1
readinessProbe:
failureThreshold: 3
httpGet:
path: /
port: 3000
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
ports:
- containerPort: 3000
# ghcr-luxfi, not ghcr-secret. lux-ns/ghcr-secret authenticates as
# Darkhorse7stars, which ghcr refuses for luxfi/lux-market -- the token
# endpoint answers 403 and the pull never starts. Every other namespace
# reads luxfi packages as hanzo-dev, which is what lux-ns/ghcr-luxfi
# holds, and hanzo/lux-market pulls this exact image with it.
imagePullSecrets:
- name: ghcr-luxfi
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
# Enforcement switch, read by the lux-fleet ApplicationSet's templatePatch --
# not by the chart. selfHeal returns a hand-edited object to what is written
# here; prune stays off, so nothing is ever deleted.
cd:
automated: false