zeekayandHanzo Dev
b1059c5e6f
deploy/lux-{mainnet,testnet}/luxd-archive.yaml are charts/app values for
the two luxd archives that serve api.lux.network, api.lux.cloud and
api.lux-test.network. They replace the hand-applied k8s/ manifests and
deploy/lux-api/route.yaml, which declared the same objects.
Rendered and dry-run against the running objects (server-side, the way
CD applies), a sync adds the chart's labels, its config checksum and
HANZO_VERSION, and nothing else: same container, genesis, chain config,
volumes and routes. So cd.automated is off until someone syncs one.
Co-authored-by: Hanzo Dev <[email protected]>
57 lines
2.9 KiB
YAML
57 lines
2.9 KiB
YAML
# lux-testnet kustomization
|
|
#
|
|
# Strict no-regression policy: only includes manifests whose git content
|
|
# matches (or is a forward-only delta of) the live in-cluster state.
|
|
# Verified via `kubectl diff -f <file>` 2026-06-01.
|
|
#
|
|
# Excluded due to pre-existing drift (sister maintainers own these):
|
|
# explorer.yaml / explorer-testnet.yaml / frontend-testnet.yaml
|
|
# — mix of aspirational + stale; would
|
|
# create new Deployments + clobber the
|
|
# live explorer pod.
|
|
#
|
|
# 2026-07-26: api-gateway-gateway-config.yaml is no longer excluded — it now
|
|
# holds the verbatim live gateway.json (kubectl diff clean) with the backend
|
|
# host moved off luxd-headless onto the ready-gated luxd Service, and the
|
|
# info/health backends moved off /ext/* onto /v1/*. luxd-statefulset.yaml is
|
|
# newly tracked for the same reason: lux-operator is 0/0, so git is the only
|
|
# durable home for the C-Chain-bootstrapped readiness gate.
|
|
#
|
|
# 2026-07-26: ingress.yaml is no longer excluded. The stale-middleware note above
|
|
# was itself stale — the live IngressRoute references cors-allow-all,
|
|
# mainpage-rewrite and blockscout-prefix-cchain, all of which exist in
|
|
# lux-testnet; there is no strip-csp anywhere on it. ingress.yaml now holds the
|
|
# verbatim live object plus the explorer.testnet.lux.network host and a real
|
|
# cert-manager Certificate, and explore-fe.yaml (new) holds the frontend that
|
|
# route depends on. Both are `kubectl diff -f` clean.
|
|
#
|
|
# 2026-07-28: exchange-api.yaml is newly tracked. It backed the public host
|
|
# api-exchange.lux-test.network while existing only as a kubectl apply, so when
|
|
# it was scaled to 0 the host served a bare 503 and nothing reconciled it back.
|
|
# Content is verbatim live (`kubectl diff -f` clean) at replicas=1.
|
|
#
|
|
# Its workload is now deploy/lux-testnet/exchange-api.yaml, and only the Ingress
|
|
# is left here, as exchange-api-ingress.yaml — moving it into the chart renames
|
|
# it, and an Ingress name is a cert-manager Certificate name. lux-indexer went
|
|
# entirely: its ConfigMap and claim are in the values file now.
|
|
#
|
|
# Sister manifest set: ../lux-mainnet/kustomization.yaml.
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
namespace: lux-testnet
|
|
resources:
|
|
- api-gateway-gateway-config.yaml
|
|
# luxd is intentionally absent here. Its only deployment source is
|
|
# deploy/lux-testnet/luxd.yaml through the lux-testnet-luxd CD Application.
|
|
- configmap.yaml
|
|
- chain-aliases.yaml
|
|
- dead-chains-cm.yaml
|
|
# heartbeat-cronjob.yaml was deleted in 96a7f61 (chain-heartbeat spoke the
|
|
# removed /ext dialect and had sent nothing for weeks) but stayed listed
|
|
# here, so `kubectl kustomize .` failed and this directory could not be
|
|
# built at all — the same failure class as mainnet's phantom indexer.yaml.
|
|
- ingress-chains.yaml
|
|
- ingress.yaml
|
|
- explore-fe.yaml
|
|
- exchange-api-ingress.yaml
|