Files
zeekayandHanzo Dev 425b96f66e the cluster is named, not addressed by a gone account
Every provenance line and manifest still named a DigitalOcean context, and
the ARC values described a pool that died with it. A cluster gets a name
here; the address it answers on belongs to the private record.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-16 16:15:33 -07:00

41 lines
1.1 KiB
YAML

---
###############################################################################
# IngressRoutes: Bridge (lux-k8s)
# TLS via hanzoai/ingress ACME certResolver with Cloudflare DNS challenge.
#
# NOTE: Must use hanzo.ai/v1alpha1 IngressRoute CRD (NOT standard K8s Ingress).
# lux-k8s uses hanzo.ai CRD group.
#
# DNS: bridge.lux.network -> 134.199.138.27 (lux-k8s hanzoai/ingress LB)
# Cluster: lux-k8s (lux-k8s)
###############################################################################
# bridge.lux.network -> bridge-ui:3000 (Next.js frontend)
# bridge-api.lux.network -> bridge-server:3000 (Go API server)
apiVersion: hanzo.ai/v1alpha1
kind: IngressRoute
metadata:
name: lux-bridge
namespace: lux-bridge
labels:
app: lux-bridge
spec:
entryPoints:
- websecure
routes:
- kind: Rule
match: Host(`bridge.lux.network`)
services:
- name: bridge-ui
port: 3000
- kind: Rule
match: Host(`bridge-api.lux.network`)
services:
- name: bridge-server
port: 3000
tls:
certResolver: letsencrypt
domains:
- main: bridge.lux.network
- main: bridge-api.lux.network