Re: [I] feat: In version 3.9.1 apisix, multiple ingress controllers are deployed in the same K8S cluster, corresponding to the same set of etcds, and consul is used for service discovery, and some apisix pods are forwarded after rolling updates, and the upstream node is considered unavailable and thus 503 [apisix-ingress-controller]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on issue #2340:
URL: https://github.com/apache/apisix-ingress-controller/issues/2340#issuecomment-2749804509

   This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org