Add origin readiness endpoint #373
Merged
Conversation
This file contains 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
Anton-Kalpakchiev
force-pushed
the
origin-is-ready
branch
2 times, most recently
from
f19a0b2 to
1f56163
Compare
Anton-Kalpakchiev
force-pushed
the
backend-is-ready
branch
from
df51ec9 to
b32b3e1
Compare
Anton-Kalpakchiev
force-pushed
the
origin-is-ready
branch
from
1f56163 to
fee2dd4
Compare
Anton-Kalpakchiev
force-pushed
the
origin-is-ready
branch
from
fee2dd4 to
f7a1b54
Compare
gkeesh7
approved these changes
Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As described in #371, all services should implement a "readiness" endpoint, which checks whether the service is ready to serve traffic, i.e. whether it can reach all of its dependencies.
Add readiness endpoint for origin, which checks whether all its backends are reachable.
Stacked on top of #372