vortegatorres commented on issue #2708: URL: https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-4435006610
Following up on your earlier suggestion (@AlinsRan): > Using health check ups can alleviate this issue. We enabled active health checks on the affected upstream about 3 weeks ago. The same underlying behavior described in this issue persists, and the health check has introduced an additional failure mode. ## Environment APISIX Helm chart 2.13.0, standalone mode, backends listening on port 8080. ## Example Example of the situation that keeps happening with` IP-A`: - APISIX access logs show `IP-A:8080` serving successful responses (status 200) up to a specific minute. - Shortly after, the IP stopped appearing in any backend workload's logs. - The Pod was terminated as part of the rolling deploy. - APISIX continued active health-checking `IP-A:8080` for approximately 85 minutes after the Pod no longer existed. Any update about this issue? -- 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]
