unkinben 3990fbfe06 feat(vault): switch to Kubernetes service registration (#171) ...

Replaces Consul service registration with the native Kubernetes provider so Vault labels its own pods with active/standby/perf-standby status without requiring a Consul dependency.

## Changes
- `values.yaml`: swap `service_registration "consul"` for `service_registration "kubernetes" {}`, add `VAULT_K8S_NAMESPACE` and `VAULT_K8S_POD_NAME` env vars via downward API
- `role_k8s-service-registration.yaml`: Role + RoleBinding granting the `vault` service account `get`/`update`/`patch` on pods
- `kustomization.yaml`: include new RBAC file

Reviewed-on: #171

2026-05-26 00:06:56 +10:00

..

gateway.yaml

fix(gateways): add explicit group: "" to all certificateRefs entries (#153)

2026-05-23 23:47:24 +10:00

httproute.yaml

fix(gateways): add explicit group/kind/weight to all HTTPRoute refs (#162)

2026-05-24 20:32:37 +10:00

kustomization.yaml

feat(vault): switch to Kubernetes service registration (#171)

2026-05-26 00:06:56 +10:00

namespace.yaml

feat(vault): deploy HashiCorp Vault 2.0.1 via Helm chart (5-replica HA raft) (#148)

2026-05-23 22:39:41 +10:00

role_k8s-service-registration.yaml

feat(vault): switch to Kubernetes service registration (#171)

2026-05-26 00:06:56 +10:00