Files
zeekayandHanzo Dev 73c8612fb1 dex: same venue cutover for testnet + devnet
Same rename as lux-mainnet: dchain-venue -> dex on the canonical
ghcr.io/luxfi/dex image, zapdb on a PVC. One app shape on all three
fleets.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-05 18:43:19 -07:00

56 lines
1.2 KiB
YAML

# D-Chain DEX venue — dexd, THE dex binary from THE dex image (ghcr.io/luxfi/dex).
# ZAP :9099 is the dial-able venue endpoint for C-Chain DEX settlement once
# --dex-validator turns on; nothing dials it until then. Chainstate lives on a
# PVC: the venue's zapdb is authoritative once markets exist (its predecessor,
# dchain-venue, kept it on an emptyDir — wiped on every reschedule).
replicas: 1
selectorLabels:
app: dex
containerName: dex
image:
repository: ghcr.io/luxfi/dex
tag: v1.14.3
pullPolicy: IfNotPresent
labels:
lux.network/component: dex
partOf: lux
command:
- /usr/local/bin/dexd
args:
- run
- -addr
- 0.0.0.0:9099
- -db
- /data/db
ports:
- containerPort: 9099
name: zap
persistence:
enabled: true
name: data
mountPath: /data
size: 10Gi
# image runs as dexd (uid 1000); without fsGroup a fresh PVC mounts root-owned
# and the zapdb open fails.
fsGroup: 1000
readinessProbe:
tcpSocket:
port: 9099
initialDelaySeconds: 3
periodSeconds: 5
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 3
resources:
requests:
cpu: 100m
memory: 256Mi
limits:
cpu: '1'
memory: 1Gi
imagePullSecrets:
- name: ghcr-luxfi
topologySpread:
enabled: false
terminationGracePeriodSeconds: 30