Use /readyz for 1.7.3 onwards #124
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
|
Could you fix the failing unit test and add an integration test that a multi node cluster can be created and a rolling update works? |
mrIncompetent
force-pushed
the
readyz
branch
2 times, most recently
from
6e93e76 to
7a1a26f
Compare
bashofmann
approved these changes
Jan 2, 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.
The /readyz endpoints only reports success when all sharts on the node have been fully replicated. This ensures availability during a rolling update.
This functionality was tested by continously restarting a StatefulSet for 1h, while running bfb against the cluster. Testing manifests can be found in https://github.com/qdrant/qdrant-helm/tree/update-validation