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

/readiness endpoint #213

Closed
nhoening opened this issue Oct 16, 2021 · 1 comment
Closed

/readiness endpoint #213

nhoening opened this issue Oct 16, 2021 · 1 comment

Comments

@nhoening
Copy link
Contributor

This endpoint can be used to monitor if the container could perform its jobs.

From a Kubernetes-bases article:

Readiness probe. This is for detecting whether the application is ready to handle requests. If a readiness probe fails, Kubernetes will leave the pod running, but won't send any requests to the pod.

I'm considering whether this would be a good (central) place for monitoring if all tasks have been run in a sufficient manner. If not, we can also add a different endpoint for that, e.g. /completeness

@nhoening
Copy link
Contributor Author

nhoening commented Jul 5, 2022

We got /api/v3_0/health/ready, from #416 so I am closing this.

@nhoening nhoening closed this as completed Jul 5, 2022
Containerisation automation moved this from In progress to Done Jul 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

1 participant