VanLiuZhi opened a new issue, #2231:
URL: https://github.com/apache/apisix-ingress-controller/issues/2231
### Issue description
I have deployed two Ingresses, and I am now using the ingressClass to
publish routes to two controllers, now everything is fine.
If I change the ingressClass of route A to the same as route B, both
Ingresses will have this record, which means that route A will not delete it.
route A
```
apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
name: apisix-dashboard-rd
namespace: ingress-apisix
spec:
ingressClassName: apisix-rd
http:
- backends:
- serviceName: apisix-dashboard
servicePort: 80
match:
hosts:
- apisix-admin-rd.test.com
paths:
- /*
name: route
```
route B
```
apiVersion: apisix.apache.org/v2
kind: ApisixRoute
metadata:
name: apisix-dashboard
namespace: ingress-apisix
spec:
ingressClassName: apisix
http:
- backends:
- serviceName: apisix-dashboard
servicePort: 80
match:
hosts:
- apisix-admin.test.com
paths:
- /*
name: route
```
The general workflow;
```
routeA => ingressClassName: apisix-rd
routeB => ingressClassName: apisix
ingressA route list => [ apisix-dashboard-rd ]
ingressB route list => [ apisix-dashboard ]
change routeA：
routeA => ingressClassName: apisix
routeB => ingressClassName: apisix
ingressA route list => [ apisix-dashboard-rd ]
ingressB route list => [ apisix-dashboard, apisix-dashboard-rd ]
```
I suspect that there is a data synchronization issue. After adjusting the
synchronization parameters:
```
kubernetes:
kubeconfig: ""
resync_interval: "60s"
```
I found that the route information remains unchanged after the data is
updated.
Is it designed this way, or is it a bug?
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
apisix-ingress-controller version: 1.7.1
Kubernetes: 1.26.10
apisix: 3.8.0
linux: 4.18.0 x86_64
--
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]
