Merged
Conversation
Makes the management server expose dedicated endpoints for checking readiness and liveness. This allows for a distinction between an app that is up and running and one that is ready to take on traffic.
Leverages readiness information when running system tests. The information is provided by dedicated health endpoints.
Ensures that when a node cannot get configured (for whatever reason) the corresponding error gets logged.
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.
Enables a readiness endpoint for the management server of the message broker. Makes use of that during system tests to avoid the node not being able to serve traffic even though it is labeled
healthy.Fixes #256 .