Files
universe/deploy/lux-bridge/bridge-ui.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

57 lines
1.5 KiB
YAML

# Generated from the live lux-bridge/bridge-ui 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: 2
selectorLabels:
app: bridge-ui
containerName: ui
image:
repository: ghcr.io/luxfi/bridge-ui
digest: sha256:71e0bbe79a37613887748eae2fec3a0c0caae50cded0eec29439a32c12e6f9d4
pullPolicy: Always
env:
- name: NEXT_PUBLIC_BRIDGE_API
value: https://bridge-api.lux.network
- name: NEXT_PUBLIC_BACKEND_API
value: https://bridge-api.lux.network
- name: NEXT_PUBLIC_IDENTITY_API
value: https://bridge-api.lux.network
- name: NEXT_PUBLIC_EXPLORER_API
value: https://bridge-api.lux.network
- name: NEXT_PUBLIC_NETWORK_NAME
value: mainnet
resources:
limits:
cpu: 500m
memory: 512Mi
requests:
cpu: 250m
memory: 256Mi
readinessProbe:
failureThreshold: 3
initialDelaySeconds: 10
periodSeconds: 15
successThreshold: 1
tcpSocket:
port: 3000
timeoutSeconds: 1
ports:
- containerPort: 3000
name: http
servicePort: 80
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30
imagePullSecrets: []
# Enforcement switch, read by the lux-fleet ApplicationSet's templatePatch —
# not by the chart. On while this Application already read Synced, so it
# applies nothing today; what it adds is selfHeal, which returns a
# hand-edited object to what is written here. prune stays off.
cd:
automated: false