Repository navigation
Check the database in a readiness endpoint - #16
Merged
Merged
Conversation
/health stays a liveness check. /health/ready also opens a connection to PostgreSQL and answers 503 when it cannot, so an orchestrator stops sending traffic to an instance that has lost its database.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
GET /health/readyopens a connection to PostgreSQL and answers 503 when it can't. It's for a readiness probe, so an orchestrator stops sending traffic to an instance that has lost its database.GET /healthstays a liveness check and doesn't touch the database.Tests
/healthstays 200.