We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Branched off from https://github.com/neondatabase/cloud/issues/14114
At this moment, we can only rely on k8s's signal for compute unavailability, specifically, container process monitoring.
We would like to have an end-to-end healthcheck, which would allow us to detect problems, such as:
We have a healthcheck mechanism, allowing us to detect compute issues within <30s, and taking appropriate actions, such as restarting.
We should have a piece of code inside vm which would respond to a healthcheck.
The text was updated successfully, but these errors were encountered:
Not sure we will need that or if Kubernetes is good enough. Putting in the backlog for now.
Sorry, something went wrong.
No branches or pull requests
Problem description / Motivation
Branched off from https://github.com/neondatabase/cloud/issues/14114
At this moment, we can only rely on k8s's signal for compute unavailability, specifically, container process monitoring.
We would like to have an end-to-end healthcheck, which would allow us to detect problems, such as:
Feature idea(s) / DoD
We have a healthcheck mechanism, allowing us to detect compute issues within <30s, and taking appropriate actions, such as restarting.
Implementation ideas
We should have a piece of code inside vm which would respond to a healthcheck.
The text was updated successfully, but these errors were encountered: