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
This caused the pod to be restarted when the database was under maintenance. The liveness probe returned this:
sh-4.4$ curl http://localhost:8080/health/live {"details":"Error id d1a65d60-fe15-4267-8014-e2aa67ea96ec-4","stack":""}
and after a few failures the pod was killed.
As per best practices, the liveness probe should not fail if the db is down, only the readiness.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
This caused the pod to be restarted when the database was under maintenance. The liveness probe returned this:
and after a few failures the pod was killed.
As per best practices, the liveness probe should not fail if the db is down, only the readiness.
The text was updated successfully, but these errors were encountered: