explore/deploy/k8s/explore-fe/kustomization.yaml at main

mirror of https://github.com/luxfi/explore.git synced 2026-09-24 00:28:18 +00:00

Files

T

zeekayandHanzo Dev 31deee7551 fix(deploy): dedicated api-explore.lux.network ingress with letsencrypt-prod TLS

The explorer Go backend answers by Host header via the ingress default backend,
so api-explore.lux.network responded 200 with no ingress rule — but with no TLS
block for that SNI the controller served the self-signed INGRESS DEFAULT CERT,
which browsers reject (ERR_CERT_AUTHORITY_INVALID). The explorer FE was stuck in
skeleton loaders. Add a dedicated Ingress -> explorer-unified:8090 with a
letsencrypt-prod TLS block (mirrors api-explore.osage.network). Verified live:
explore.lux.network now loads live blocks/txns/stats (ssl_verify_result=0).

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-15 18:13:04 -07:00

15 lines

493 B

YAML

Raw Permalink Blame History

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

 # Per-brand × per-env explore frontend, decomposed.
 #
 # Image is brand-only (ghcr.io/{org}/explore:vX.Y.Z); env (NETWORK_ID,
 # IS_TESTNET, *_HOST, RPC_URL) lives in ConfigMaps mounted via
 # Deployment.envFrom. Same image runs mainnet+testnet — only the
 # ConfigMap differs.
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 resources:
   - configmap-mainnet.yaml
   - configmap-testnet.yaml
   - deployments-mainnet.yaml
   - deployments-testnet.yaml
   - ingress-api-mainnet.yaml

15 lines 493 B YAML Raw Permalink Blame History Unescape Escape

15 lines

493 B

YAML

Raw Permalink Blame History