chore(health): add dedicated liveness and readiness endpoints #1987
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.
Description & motivation
When Redis fails, but Postgres is still responding, the existing liveness probe continues responding and indicating the server was healthy.
We need a more complex query to account for the state of Redis as well as Postgres when determining if the server is alive and ready to accept traffic (healthy).
Changes:
/liveness
endpoint/readiness
endpointTo-do before merge:
Screenshots:
Validation of changes:
Checklist:
References