Files
zeekayandClaude Opus 5.5 d3db69745e lux-safe-cgw runs on AWS, so the LAN runs none
safe-cgw.lux.network is served by two replicas on AWS, declared by the overlay
hanzoai/universe infra/aws/values/hanzo/lux-safe-cgw.yaml over this file, which
also pins v0.1.6 by digest.

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_016dDw5Lp9sZFctwvZLn4nVz
2026-09-22 23:41:52 -07:00

67 lines
1.4 KiB
YAML

# CD applies this file within ~90s, so THIS is the source now, not the cluster.
# Without this the app is manual-sync: the gateway ran v0.1.2 for weeks while
# this file said v0.1.5, and nothing was wrong except that nobody had pressed
# sync. prune stays off (the chart is not the only owner of objects in the
# namespace); selfHeal returns a hand-edited Deployment to what is written here.
cd:
automated: false
# Runs on AWS (hanzoai/universe infra/aws/values/hanzo/lux-safe-cgw.yaml); the LAN runs none.
replicas: 0
selectorLabels:
app: lux-safe-cgw
containerName: cgw
image:
repository: ghcr.io/luxfi/safe-cgw
tag: v0.1.6
pullPolicy: Always
partOf: lux-safe
env:
- name: PORT
value: '3000'
resources:
limits:
memory: 64Mi
requests:
cpu: 25m
memory: 32Mi
livenessProbe:
failureThreshold: 3
httpGet:
path: /health
port: 3000
scheme: HTTP
initialDelaySeconds: 5
periodSeconds: 30
successThreshold: 1
timeoutSeconds: 1
readinessProbe:
failureThreshold: 3
httpGet:
path: /health
port: 3000
scheme: HTTP
initialDelaySeconds: 2
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 1
ports:
- containerPort: 3000
name: http
servicePort: 80
imagePullSecrets:
- name: ghcr-secret
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
ingress:
enabled: true
hosts:
- safe-cgw.lux.network
tls: true
className: ingress