Horus-K opened a new issue, #1122:
URL: https://github.com/apache/apisix-ingress-controller/issues/1122
### Issue description
First create an ApisixRoute of http,
Then create the ApisixRoute of tcp, both use the same svc,
After the first http ApisixRoute is deleted, the tcp ApisixRoute cannot be
used.
At this time, check that apisix upstream has been deleted
Reverse the order of deletion, it will not appear
This won't happen if you use two svc
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long): 1.4.1
- apisix 2.13.0
- your Kubernetes cluster version (output of kubectl version): 1.20
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
### Minimal test code / Steps to reproduce
1.create svc
```
apiVersion: v1
kind: Service
metadata:
name: sentinel-test
namespace: sentinel
spec:
ports:
- name: t1
protocol: TCP
port: 8080
targetPort: 8080
selector:
app: sentinel-test
type: ClusterIP
sessionAffinity: None
```
2 create http ApisixRoute
```
apiVersion: apisix.apache.org/v2beta3
kind: ApisixRoute
metadata:
name: sentinel-test
namespace: sentinel
spec:
http:
- backends:
- serviceName: sentinel-test
servicePort: 8080
match:
hosts:
- sentinel.api.xxx.com
paths:
- /*
name: sentinel-test
```
3.create tcp ApisixRoute
```
apiVersion: apisix.apache.org/v2beta3
kind: ApisixRoute
metadata:
name: sentinel-test-route
namespace: sentinel
spec:
stream:
- backend:
serviceName: sentinel-test
servicePort: 8080
match:
ingressPort: 8080
name: sentinel-test
protocol: TCP
```
4 now check upstream
5 delete http ApisixRoute
check upstream
now the tcp ApisixRoute cannot be used.
### Actual result
The log is normal
### Error log
no
### Expected result
It will not affect other routes after deletion
--
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]
