You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and I made some modification envoy.json to use overload_manager (envoy.overload_actions.stop_accepting_requests) future.
when overload_actions triggered, its started to block some percent of requests. But unexpectedly, its blocking the requests coming from the probs too. envoyproxy/envoy#23843
Is there any other way, we can perform healthcheck on emissary-ingress instead (/ambassador/v0/check_ready, /ambassador/v0/check_alive) ?
Hi, I am working on emissary-ingress for quite sometime and configured the setup in kubernetes with below probs.
and I made some modification envoy.json to use overload_manager (envoy.overload_actions.stop_accepting_requests) future.
when overload_actions triggered, its started to block some percent of requests. But unexpectedly, its blocking the requests coming from the probs too. envoyproxy/envoy#23843
Is there any other way, we can perform healthcheck on emissary-ingress instead (/ambassador/v0/check_ready, /ambassador/v0/check_alive) ?
There is something /ready endpoint which is exposed by admin port (8001), mentioned in the below document. Can we use this to perform readiness check ? https://www.getambassador.io/docs/emissary/latest/release-notes
The text was updated successfully, but these errors were encountered: