Stéphane Tailland 01f873b773 Bind the Gateway TLS secret to Konnect via KongCertificate/KongSNI ...

Gateway API's listeners[].tls.certificateRefs never gets synced to
Konnect by the gateway operator in this setup — same working pattern
as every other resource here (KongService, KongRoute, ...): a
Kong-native CRD, not the Gateway API's own translation.

2026-08-21 09:47:29 +02:00

..

audit-log.yaml

MCP server

2026-08-20 16:26:48 +02:00

certificate.yaml

Bind the Gateway TLS secret to Konnect via KongCertificate/KongSNI

2026-08-21 09:47:29 +02:00

kongplugin.yaml

MCP server

2026-08-20 16:26:48 +02:00

path-rewrite-bindings.yaml

Expose catalog-api under /catalog/v1, decoupled from the backend path

2026-08-21 09:22:33 +02:00

path-rewrite.yaml

Expose catalog-api under /catalog/v1, decoupled from the backend path

2026-08-21 09:22:33 +02:00

pluginbindings.yaml

MCP server

2026-08-20 16:26:48 +02:00

proxy-cache.yaml

MCP server

2026-08-20 16:26:48 +02:00

rate-limiting.yaml

MCP server

2026-08-20 16:26:48 +02:00

routes.yaml

Expose catalog-api under /catalog/v1, decoupled from the backend path

2026-08-21 09:22:33 +02:00

service.yaml

MCP server

2026-08-20 16:26:48 +02:00