Buggy behavior after failed health check recover

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

3.5.0 (With KIC 2.12)

Current Behavior

Sometimes when health check fails and health check recovers Kong response is still 503 for that service

Expected Behavior

Response recovers while Health check recovers

Steps To Reproduce

1. In K8s environment
2. Bring up a project and create a Ingress and UpstreamPolicy (With TCP or HTTP health check [TCP Preferred])
3. configure health check to failure for some time (you will get 503 error)
4. make that health check to success again (you may get 503 error again

Anything else?

No response