mirror of
https://github.com/luxfi/charts.git
synced 2026-09-24 00:24:06 +00:00
zeekayandHanzo Dev
71d0146c08
hanzo-build-linux-amd64, lux-build-linux-amd64, zoo-build-linux-amd64 and every other org-prefixed spelling all meant the same machine. Which org a job belongs to does not change which host can build it, so the org bought one pool name per org per arch and each could go stale on its own -- the evo host alone answered to fourteen names for one label. One vocabulary now: linux-amd64, linux-arm64, macos-arm64, win-amd64. The generic labels every plain workflow uses (ubuntu-latest, self-hosted) are untouched, so naive CI keeps working. Co-authored-by: Hanzo Dev <[email protected]>
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