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
I'm running multiple APISIX Ingress Controller in the same cluster. I'm specifying namespaceSelector because resources need to be isolated at the namespace level, but it seems to be working differently in version 1.7.0 and version 1.8.0.
For example, two namespaces are each
metadata:
name: Alabels:
gateway.apache.org/type: GLOBALgateway.apache.org/env: DEV
metadata:
name: Blabels:
gateway.apache.org/type: OPENAPIgateway.apache.org/env: DEV
Version 1.7.0 of Ingress Controller reads only resources deployed in B Namespace,
while version 1.8.0 of Ingress Controller reads all resources deployed in A and B Namespace.
There are no documents involved, so it is necessary to check that this is the intended action.
Environment
your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.7.0/1.8.0
your Kubernetes cluster version (output of kubectl version): 1.29.6
if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a): AWS EKS
The text was updated successfully, but these errors were encountered:
This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.
Issue description
I'm running multiple APISIX Ingress Controller in the same cluster. I'm specifying
namespaceSelector
because resources need to be isolated at the namespace level, but it seems to be working differently in version 1.7.0 and version 1.8.0.For example, two namespaces are each
It has a label like and it's a namepace Selector
Assuming that you have designated it as,
Version 1.7.0 of Ingress Controller reads only resources deployed in B Namespace,
while version 1.8.0 of Ingress Controller reads all resources deployed in A and B Namespace.
There are no documents involved, so it is necessary to check that this is the intended action.
Environment
The text was updated successfully, but these errors were encountered: