request help: 2个apisix-ingress-controller用同一个etcd时候无法隔离

[lihuawei321]

Issue description

当我在一个k8s环境的2个命名空间各自部署一套apisix（包括ingress和dashboard），但是2套apisix用的同一个etcd，但是是不同的prefix。每个命名空间有不同的apisix.ingress的label，并且ingress-controller的配置里也配置不同的 app_namespaces和 namespace-selector。但是当我在其中一个命名空间里创建apisixroute和apisixupstream时候，2个命名空间下的apisixdashboard有对方命名空间的apisixroute和apisixupstream。查看etcd时候，2个prefix下都有同样的route和upstream。 就是当2个apisix使用同一个etcd时候，互相会有冲突。

Environment

• your apisix-ingress-controller version (output of apisix-ingress-controller version --long): 1.4.1
• your Kubernetes cluster version (output of kubectl version): 1.20.10
• if you run apisix-ingress-controller in Bare-metal environment, also show your OS version (uname -a):

[AlinsRan]

In fact, the apisix-ingress-controller is not aware of etcd. The app_namespaces has been deprecated. Maybe it was affected by this bug #1238 .

[AlinsRan]

The problem of namespace-selector invalid will be fixed in v1.5.0. You can use ingress resources, and then isolate resources through different IngressClass.

[tao12345666333]

Please refer to #592

[lihuawei321]

The problem of namespace-selector invalid will be fixed in v1.5.0. You can use ingress resources, and then isolate resources through different IngressClass.

我用了ingressclass，也是2个命名空间下的apisixdashboard都会创建。

[github-actions[bot]]

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[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.