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.

This commit is contained in:

Ben Vincent

2026-07-25 17:06:09 +10:00

parent a633835550

commit 3d2bdec0b8

3 changed files with 30 additions and 4 deletions

									
										apps/base/consul/kustomization.yaml
									
		+1
		
												View File
												
				@@ -6,5 +6,6 @@ resources:

				  - namespace.yaml

				  - gateway.yaml

				  - httproute.yaml

				  - service.yaml

				  - vaultauth.yaml

				  - vaultstaticsecret.yaml