40 lines
1.9 KiB
YAML
40 lines
1.9 KiB
YAML
# lux-devnet kustomization
|
|
#
|
|
# Strict no-regression policy (same contract as ../lux-mainnet and
|
|
# ../lux-testnet): only manifests whose git content matches the live
|
|
# in-cluster state are listed. Every entry was proven with
|
|
# `kubectl diff -f <file>` returning empty AND a mutated copy diffing as the
|
|
# positive control, 2026-07-28.
|
|
#
|
|
# NOT listed, with reasons:
|
|
# explorer.yaml / explorer-devnet.yaml / frontend-devnet.yaml /
|
|
# lux-indexer.yaml / ingress.yaml / ingress-chains.yaml / explore-fe.yaml
|
|
# — pre-existing drift against live (sister maintainers
|
|
# own these surfaces); adding them would clobber live
|
|
# deployments. Same exclusion class as testnet's.
|
|
# snapshot-native/ — imperative recovery tooling, not declarative state.
|
|
#
|
|
# DELETED 2026-07-28 (do not resurrect):
|
|
# luxd-startup.yaml + scripts/ — the CM-based startup path is RETIRED on
|
|
# devnet: no `luxd-startup` ConfigMap exists live and the StatefulSet's
|
|
# startup is rendered INLINE by lux-operator from the LuxNetwork CR
|
|
# (network.yaml). Worse, both copies asked for --consensus-quorum-size=3,
|
|
# which at --consensus-sample-size=5 is 60% < 2/3 and breaks BFT safety;
|
|
# the live fleet runs quorum 4 (ceil(2*5/3)+1). A dead file carrying an
|
|
# unsafe consensus flag is a landmine, not documentation.
|
|
# watchdog.yaml — the luxd-watchdog CronJob was deliberately removed from
|
|
# the live cluster (watchdog stays suspended per the launch protocol);
|
|
# the file would have re-created it UNSUSPENDED.
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
namespace: lux-devnet
|
|
resources:
|
|
# luxd is intentionally absent here. Its only deployment source is
|
|
# deploy/lux-devnet/luxd.yaml through the lux-devnet-luxd CD Application.
|
|
- luxd-genesis.yaml
|
|
- chain-aliases.yaml
|
|
- configmap.yaml
|
|
- api-gateway-gateway-config.yaml
|
|
- explore-ingressroute.yaml
|
|
- exchange-api.yaml
|