Stéphane Tailland fa7abfe5bd Drop the manual KongCertificate/KongSNI workaround ...

Turned out unnecessary: the real blocker was the missing
konghq.com/secret=true label on the Vault-sourced Secret, not a gap
in the Gateway API TLS translation itself. Once that label was added
(k8s-platform), the operator's own auto-generated KongCertificate/SNI
started working and this manual one just collided with it.

2026-08-21 09:51:23 +02:00

..

mcp

Point catalog-api at the classic-models Keycloak realm, drop separate MCP hostname

2026-08-21 09:24:18 +02:00

rest

Drop the manual KongCertificate/KongSNI workaround

2026-08-21 09:51:23 +02:00

kustomization.yaml

Drop the manual KongCertificate/KongSNI workaround

2026-08-21 09:51:23 +02:00