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
I'm in need of using envoy overload manager feature (envoy.overload_actions.stop_accepting_requests) to block some percent of request when cpu usage is too high and I made some modification on envoy.json to use the same.
when overload_actions triggered, its started to block some percent of requests. But unexpectedly, readiness and liveness probes (/ambassador/v0/check_ready, /ambassador/v0/check_alive) also getting failed.
Is there any other way, we can perform healthcheck on emissary-ingress instead (/ambassador/v0/check_ready, /ambassador/v0/check_alive) ?
The text was updated successfully, but these errors were encountered:
Those are the only health-check endpoints I know of. I'm not sure there's another way to access the readiness/liveness probes if blocked by a custom config. Will mark this as a feature request. You could look at Active Health Checking w/ the Endpoint Resolver.
Hi, I am working on emissary-ingress for quite sometime and configured the setup in kubernetes with below probs.
I'm in need of using envoy overload manager feature (envoy.overload_actions.stop_accepting_requests) to block some percent of request when cpu usage is too high and I made some modification on envoy.json to use the same.
when overload_actions triggered, its started to block some percent of requests. But unexpectedly, readiness and liveness probes (/ambassador/v0/check_ready, /ambassador/v0/check_alive) also getting failed.
Is there any other way, we can perform healthcheck on emissary-ingress instead (/ambassador/v0/check_ready, /ambassador/v0/check_alive) ?
The text was updated successfully, but these errors were encountered: