bearchess opened a new issue, #10422: URL: https://github.com/apache/apisix/issues/10422
### Current Behavior I am currently using APIsix and Nacos in Kubernetes. APIsix service discovery is configured with Nacos. However, after a pod update and restart in K8s, APIsix still retrieves the old pod IP, resulting in a 503 error upon access. This issue is resolved upon restarting APIsix, and it is currently not reproducible. ### Expected Behavior _No response_ ### Error Logs [error] 45#45: *59314180 upstream timed out (110: Operation timed out) while connecting to upstream, client: 8.132.18.129, server: _, request: "GET /micro-user/system HTTP/1.1", upstream: "http://172.17.97.37:18081/micro-user/system/";, host: "https://www.test.com";, referrer: "https://www.test.com/"; ### Steps to Reproduce onloy one step update an image in Kubernetes deployment ### Environment - APISIX version (run `apisix version`):2.14.2 - Operating system (run `uname -a`): Linux apisix-5f5bc75b47-dp2cb 5.10.134-15.1.2.lifsea8.x86_64 #1 SMP Tue Aug 29 07:26:14 UTC 2023 x86_64 Linux - OpenResty / Nginx version (run `openresty -V` or `nginx -V`): openresty/1.19.9.1 - etcd version, if relevant (run `curl http://127.0.0.1:9090/v1/server_info`): - APISIX Dashboard version, if relevant: - Plugin runner version, for issues related to plugin runners: - LuaRocks version, for installation issues (run `luarocks --version`): -- 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]
