suninuni opened a new issue #632: URL: https://github.com/apache/apisix-ingress-controller/issues/632
### Issue description When upstream service is rolling update, Apisix can not update upstream nodes immediately which caused request failed with 502. This will not happen in ingress-nginx-controller(version 0.46 which is already cancelled reload nginx when upstream nodes changed.)  ### Environment * your apisix-ingress-controller version (output of `apisix-ingress-controller version --long`); 0.6.0 * your Kubernetes cluster version (output of `kubectl version`); 1.21.0 ### Minimal test code / Steps to reproduce the issue 1. install by default values.yml 2. deploy a service by simple configure. 3. trigger a rolling update and run with ab in the same time. ### What's the actual result? (including assertion message & call stack if applicable) For Apisix, the Non-2xx responses will around 1000, but for ingress-nginx-controller, this will be 0. ### What's the expected result? No failed request when upstream nodes changed. -- 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]
