Add liveness and readiness HTTP endpoints#1239
Draft
emersonian wants to merge 1 commit into
Draft
Conversation
For container orchestrators like Kubernetes to know if Zaino is alive and synced, ready for end-user traffic. - New opt-in HTTP server on a dedicated port (health.listen_addr, disabled by default). - Readiness is decided by proximity to the chain tip (blocks-behind plus tip-age), like Zebra. This avoids ready-state flapping when the chain isn't perfectly at the tip. - Endpoint names (/livez, /readyz) follow the Kubernetes API-server convention; configuration style ([health] section) mirrors Zebra.
Member
|
Moving this to draft until we address #1311 |
zancas
marked this pull request as draft
June 27, 2026 01:01
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
3 participants
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.
For container orchestrators like Kubernetes to know if Zaino is alive and synced, ready for end-user traffic.
Reference zcash-stack for examples of how we use this in production for Zec.rocks:
Related: