Donghui0 opened a new issue #540:
URL: https://github.com/apache/apisix-ingress-controller/issues/540


   ### Issue description
   Delete the service  resource first, then delete the apisixroute, and the 
apisix controller will throw an exception:
   
![image](https://user-images.githubusercontent.com/7134928/121335331-106a5180-c94d-11eb-8197-e80a3fa3b6ef.png)
   
   When creating a new apisixroute resource, the name of spec.http.name will 
change again, which will result in a lot of historical routes remaining.
   
   
![image](https://user-images.githubusercontent.com/7134928/121335848-8a023f80-c94d-11eb-9925-ecbbbbc02e81.png)
   
   
   ### Environment
   
   * your apisix-ingress-controller version: v0.6
   * your Kubernetes cluster version (output of `kubectl version`): v1.16.9
   
   ### Minimal test code / Steps to reproduce the issue
   1.  delete service resource
   2.  delete apisix route resource
   3.  observe the controller log...
   
   ### What's the actual result? (including assertion message & call stack if 
applicable)
   apisixroute resource failed to delete.
   
   ### What's the expected result?
   apisixroute delete success.
   
   
   PS:
   If I reverse the order of deletion, can it solve the problem?


-- 
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to