You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a problem when using cert-manager with gateway api support, because it will define the temporary HTTPRoute with an explicit namespace parameter.
Expected Behavior
As the backendref is referencing a service in the same namespace I expect a 200 OK response. There should not be a difference in omitting the namespace or specifying the same namespace.
Steps To Reproduce
Given a kong gateway
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
name: kong-mgmt
namespace: kong-mgmt
spec:
gatewayClassName: kong
listeners:
- name: proxy
port: 80
protocol: HTTP
allowedRoutes:
namespaces:
from: All
Is there an existing issue for this?
Current Behavior
Access to a service with a backendRef with an namespace parameter which is the same namespace as the HTTPRoute fails with a 500 Internal Server error.
Given an HTTPRoute with namespace
some-namespace
works, but
fails with 500 Internal Server error
This is a problem when using cert-manager with gateway api support, because it will define the temporary HTTPRoute with an explicit namespace parameter.
Expected Behavior
As the backendref is referencing a service in the same namespace I expect a 200 OK response. There should not be a difference in omitting the namespace or specifying the same namespace.
Steps To Reproduce
and echo app service
and this httproute
curl -i -X GET http://echo.example.com/echo
givesHTTP/1.1 200 OK
and expected outputcurl -i -X GET http://echo.example.com/namespace
givesHTTP/1.1 500 Internal Server Error
with '{"message":"no existing backendRef provided"}'Workaround, apply a referencegrant:
Kong Ingress Controller version
Kubernetes version
Anything else?
No response
The text was updated successfully, but these errors were encountered: