carefree666 opened a new issue, #2727:
URL: https://github.com/apache/apisix-ingress-controller/issues/2727
### Issue description
Hi,
I’m currently testing Gateway API support in APISIX and have a question
regarding namespace scope.
In the official example, both the Service and HTTPRoute are created in the
ingress-apisix namespace, for example:
apiVersion: v1
kind: Service
metadata:
namespace: ingress-apisix
name: httpbin-external-domain
spec:
type: ExternalName
externalName: httpbin.org
---
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
namespace: ingress-apisix
name: get-ip
spec:
parentRefs:
- name: apisix
rules:
- matches:
- path:
type: Exact
value: /ip
backendRefs:
- name: httpbin-external-domain
port: 80
When I create HTTPRoute in a different namespace, it does not seem to take
effect.
I would like to clarify:
Is APISIX Gateway API implementation limited to resources in the
ingress-apisix namespace?
Does it support cross-namespace HTTPRoute attachment to a Gateway?
Are there specific requirements (e.g. allowedRoutes, ReferenceGrant, or
controller --watch-namespace configuration) for enabling cross-namespace
routing?
According to the Kubernetes Gateway API specification, cross-namespace
routing should be possible under certain conditions, so I want to confirm
whether this behavior is expected or if I may be missing some configuration.
Thanks for your help.
### Environment
- apisix-ingress-controller version: 2.0.0
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
