zeekayandHanzo Dev
8c6119f357
k8s/dns is re-exported from the live zones: bridge.lux.network, the ACME TXT left for bridge, bridge-api, mpc and api.mpc, lux.chat's Azure asuid records and the GoDaddy _domainconnect CNAMEs on lux.review and lux.training are gone, and lux.build lists the AWS ingress it has pointed at since 2026-09-19. kms.lux.cloud has no AWS backend: Lux's own KMS (lux-kms-go) runs on no cluster here. kms-gen-validator-keys.sh and kms-seed.sh no longer default to it; they require KMS_API_URL, because a default that does not resolve turned every key push into a "SKIP" line. NETWORKS.yaml stops listing mpc-api.lux.network, mpc.lux.network and kms.lux.cloud for the MPC topology. explore-fe-lux and explore-fe-zoo run one replica each; with maxUnavailable 1 a rollout stopped the only pod before its replacement was Ready, and the explorer answered 503 until it was. maxUnavailable is 0 now, as applied live. Co-authored-by: Hanzo Dev <[email protected]>
20 lines
533 B
YAML
20 lines
533 B
YAML
# lux-build.yaml — Cloudflare zone config for lux.build
|
|
# Zone ID: 72486d2ed359900298da1e99a0c1a0fc
|
|
# Exported from the live zone 2026-09-23; proxied A records name the AWS ingress (100.24.244.37).
|
|
---
|
|
zone: lux.build
|
|
zone_id: "72486d2ed359900298da1e99a0c1a0fc"
|
|
|
|
records:
|
|
- type: A
|
|
name: "@"
|
|
content: "100.24.244.37"
|
|
proxied: true
|
|
comment: "hanzo AWS balancer (was the LAN tunnel)"
|
|
|
|
- type: A
|
|
name: "www"
|
|
content: "100.24.244.37"
|
|
proxied: true
|
|
comment: "hanzo AWS balancer (was the LAN tunnel)"
|