Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request help: namespaceSelector #2282

Open
kworkbee opened this issue Aug 14, 2024 · 1 comment
Open

request help: namespaceSelector #2282

kworkbee opened this issue Aug 14, 2024 · 1 comment
Labels

Comments

@kworkbee
Copy link

kworkbee commented Aug 14, 2024

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

metadata:
  name: A
  labels:
    gateway.apache.org/type: GLOBAL
    gateway.apache.org/env: DEV
metadata:
  name: B
  labels:
    gateway.apache.org/type: OPENAPI
    gateway.apache.org/env: DEV

It has a label like and it's a namepace Selector

namespaceSelector:
- gateway.apache.org/type=OPENAPI
- gateway.apache.org/env=DEV

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

  • 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
Copy link

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.

@github-actions github-actions bot added the stale label Nov 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant