Route consul API hostname to the HTTP API (8500) #282

Merged
benvin merged 2 commits from benvin/consul-api-route into main 2026-07-25 18:19:39 +10:00

2 Commits

Author SHA1 Message Date
unkinben 1f501e0df3 Document ACL-authenticated API access
ci/woodpecker/pr/pre-commit Pipeline was successful
ci/woodpecker/pr/kubeconform Pipeline was successful
2026-07-25 18:15:29 +10:00
unkinben 3d2bdec0b8 Route consul API hostname to the HTTP API (8500)
Phase 2 of the consul VM->k8s migration: terraform backends, the Vault
consul secret engine, and puppet all need the consul HTTP API reachable at
consul.k8s.syd1.au.unkin.net. The Gateway/HTTPRoutes currently send both
that hostname and the consul.service.consul listener to consul-ui:80,
which serves only the UI, not the /v1 API. Consul serves the HTTP API and
the UI (/ui/) on the same port 8500, so routing everything to 8500
preserves the UI while exposing the API.

- Add a consul-http ClusterIP service selecting the consul server pods
  (app=consul, component=server, release=consul) on port 8500.
- Repoint the consul and consul-svc HTTPRoutes from consul-ui:80 to
  consul-http:8500.
2026-07-25 18:14:38 +10:00