start API server after chain init, add health/ready endpoints#623
Open
start API server after chain init, add health/ready endpoints#623
Conversation
Returns 200 with {"ready":true} when chain is initialized, 503 with
{"ready":false} otherwise. Useful for orchestration systems (e.g.,
Kubernetes readiness probes).
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.
Summary
setChain()/getChain()pattern/lean/v0/healthon metrics server (port 9668) for early liveness checks/lean/v0/readyon API server (port 9667) for readiness checksEndpoint Layout
/lean/v0/health/lean/v0/readyChanges
api_server.zig- chain now required at construction, added/lean/v0/readymetrics_server.zig- added/lean/v0/healthmain.zig- moved API server start afterbeam_node.init()Closes #519