Implement liveness check#331
Draft
victor-girardin-unity wants to merge 1 commit intoredpanda-data:masterfrom
Draft
Implement liveness check#331victor-girardin-unity wants to merge 1 commit intoredpanda-data:masterfrom
victor-girardin-unity wants to merge 1 commit intoredpanda-data:masterfrom
Conversation
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.
Previously there was no liveness probe on the Deployment, and the DaemonSet reused /ready for both probes. In OffsetsTopic scrape mode, /ready returns 503 until the consumer catches up on __consumer_offsets, which can take minutes on large clusters. Using /ready for liveness would cause Kubernetes to kill pods that are still starting up. The new /live endpoint avoids this by only checking that the HTTP server is responsive.
Work