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

78 lines
1.5 KiB
YAML

# Generated from the live lux-devnet/lux-indexer 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-indexer
network: devnet
containerName: indexerd
image:
repository: ghcr.io/luxfi/indexer
tag: 1.4.4
pullPolicy: IfNotPresent
labels:
network: devnet
args:
- -config=/etc/lux-indexer/chains.yaml
- -data=/data
- -http=:8091
env:
- name: DATA_DIR
value: /data
- name: HTTP_ADDR
value: :8091
resources:
limits:
cpu: '2'
memory: 4Gi
requests:
cpu: 200m
memory: 512Mi
volumeMounts:
- mountPath: /etc/lux-indexer
name: config
readOnly: true
- mountPath: /data
name: data
livenessProbe:
failureThreshold: 5
httpGet:
path: /health
port: http
scheme: HTTP
initialDelaySeconds: 60
periodSeconds: 30
successThreshold: 1
timeoutSeconds: 10
readinessProbe:
failureThreshold: 3
httpGet:
path: /health
port: http
scheme: HTTP
initialDelaySeconds: 15
periodSeconds: 10
successThreshold: 1
timeoutSeconds: 5
ports:
- containerPort: 8091
name: http
volumes:
- configMap:
name: lux-indexer-config
name: config
- name: data
persistentVolumeClaim:
claimName: lux-indexer-data
imagePullSecrets:
- name: ghcr-luxfi
fsGroup: 65532
podSecurityContext:
runAsUser: 65532
runAsGroup: 65532
strategy: Recreate
topologySpread:
enabled: false
lifecycle: null
terminationGracePeriodSeconds: 30