Source per-domain Gateway TLS certs from Vault instead of cert-manager

cert-manager-issued Certificates never synced to Konnect as KongCertificate
objects through the Gateway API listener path, so dataplanes fell back to
Kong's default self-signed cert. Reuse the working kong-namespace pattern
(a static wildcard cert) via ExternalSecret instead.
This commit is contained in:
Stéphane Tailland
2026-08-21 09:37:31 +02:00
parent b4fd7064a3
commit 9376bc3cb3
4 changed files with 24 additions and 18 deletions
@@ -14,7 +14,6 @@ data:
KONNECT_SERVER_URL: eu.api.konghq.com
GATEWAY_IMAGE: kong/kong-gateway:3.15
REPLICAS: "1"
TLS_ISSUER_KIND: ClusterIssuer
OIDC_ISSUER: https://keycloak.sttlab.eu/realms/sttlab # Keycloak today, but this template shouldn't assume it stays that way
CORS_ORIGINS: https://*.sttlab.local
RATE_LIMIT_MINUTE: "300"