mirror of
https://github.com/luxfi/charts.git
synced 2026-09-24 00:24:06 +00:00
zeekay
025331b27e
Chart publishing ran on a hosted runner and pushed to a pages branch, which is neither where this org builds nor where anything else it ships is fetched from. It now runs on lux-build-linux-amd64 and pushes to ghcr.io/luxfi/charts, so a chart comes from the same registry as the images it deploys. Every chart is linted and rendered against each of its values files before anything is pushed.
Lux Charts
Helm charts for Lux network infrastructure.
Charts
| Chart | Description |
|---|---|
| node | A validator — luxd, its chains and its peer identity |
The node chart
One chart serves every network that runs luxfi/node. Per-network values
select the network id and nothing else:
helm install lux oci://ghcr.io/luxfi/charts/node -f charts/node/values-lux.yaml # id 1
helm install hanzo oci://ghcr.io/luxfi/charts/node -f charts/node/values-hanzo.yaml # id 36963
helm install zoo oci://ghcr.io/luxfi/charts/node -f charts/node/values-zoo.yaml # id 200200
Lux's primary network is 1 (mainnet), 2 (testnet), 3 (local). A sovereign L1 uses its EVM id as its network id, so one number names one network wherever it appears.
The image is pinned by digest in each values file and falls back to the
chart's appVersion. Set image.digest to pin exactly; a floating tag is not
a deployable pin. Environment-specific values live in lux/universe.
Usage
helm repo add luxfi https://luxfi.github.io/charts/
helm repo update
Development
helm lint charts/node
helm template n charts/node -f charts/node/values-lux.yaml