Stéphane Tailland
fa7abfe5bd
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.
19 lines
464 B
YAML
19 lines
464 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- rest/service.yaml
|
|
- rest/routes.yaml
|
|
- rest/path-rewrite.yaml
|
|
- rest/path-rewrite-bindings.yaml
|
|
- rest/kongplugin.yaml
|
|
- rest/rate-limiting.yaml
|
|
- rest/proxy-cache.yaml
|
|
- rest/audit-log.yaml
|
|
- rest/pluginbindings.yaml
|
|
- mcp/service.yaml
|
|
- mcp/routes.yaml
|
|
- mcp/consumergroups.yaml
|
|
- mcp/ai-mcp-proxy.yaml
|
|
- mcp/openid-connect.yaml
|
|
- mcp/pluginbindings.yaml
|