Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Emissary Ingress Readiness/Liveness Probe #5588

Closed
sekar-saravanan opened this issue Mar 6, 2024 · 0 comments
Closed

Emissary Ingress Readiness/Liveness Probe #5588

sekar-saravanan opened this issue Mar 6, 2024 · 0 comments

Comments

@sekar-saravanan
Copy link
Contributor

sekar-saravanan commented Mar 6, 2024

Hi, I am working on emissary-ingress for quite sometime and configured the setup in kubernetes with below probs.

livenessProbe:
    httpGet:
        path: /ambassador/v0/check_alive
        port: 8877
        scheme: HTTP
readinessProbe:
    httpGet:
        path: /ambassador/v0/check_ready
        port: 8877
        scheme: HTTP

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

@sekar-saravanan sekar-saravanan closed this as not planned Won't fix, can't repro, duplicate, stale Mar 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant