Files
zeekayandHanzo Dev 5b3240515f k8s/boot: one coherent luxd entrypoint for all networks
luxd-boot.sh boots local/devnet/testnet/mainnet identically — the binary
(database >= v1.20.3) restores-on-boot from the S3 snapshot stream, so this
replaces the per-network startup scripts' RLP-import / peer-keysync / genesis-root
surgery with: pick network -> stage plugins -> exec luxd. Same script runs locally
and as the k8s StatefulSet entrypoint.

- luxd-boot.sh: NETWORK->id map (local|3|2|1), REPLICATE_* defaults, plugin stage.
- <net>.env: per-network config (local self-contained w/ out-of-box PQ; cluster
  nets take creds + PQ identity from KMS secrets via the operator).
- README: local + in-cluster usage.

Proven booting localnet end-to-end on luxd v1.30.6 + database v1.20.3 (P-chain up,
PQ-encrypted CDC incremental shipped).

Co-authored-by: Hanzo Dev <[email protected]>
2026-06-16 05:18:18 +00:00

13 lines
580 B
Bash

# Coherent boot — mainnet. In-cluster the operator injects REPLICATE_S3_* creds +
# the PQ identity from secrets (see lux-mainnet/snapshot-native/). This file is the
# non-secret config so a local/CI run against the cluster store stays consistent.
LUX_NETWORK=mainnet
LUXD_DATA_DIR=/data
LUXD_HTTP_PORT=9630
LUXD_STAKING_PORT=9631
REPLICATE_S3_ENDPOINT=http://s3.lux-system.svc.cluster.local:9000
REPLICATE_S3_BUCKET=lux-snapshots
REPLICATE_S3_REGION=us-central1
REPLICATE_S3_USE_SSL=false
# REPLICATE_S3_ACCESS_KEY / _SECRET_KEY / REPLICATE_AGE_IDENTITY come from KMS secrets.