-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(proof_data_handler): add a health check endpoint to the proof data handler #2278
Conversation
d5924e9
to
e29c022
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@popzxc @RomanBrodetski is it too hacky? Should I use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should use health check instead indeed. Let's not mix approaches.
Moreover, healthcheck layer is added unconditionally in the node, so isn't it already covered? |
Not sure. Proof-data-handler is started like so https://github.com/matter-labs/gitops-kubernetes/blob/main/apps/environments/era-stage-proofs/server-v2/server-v2-proof-data-handler.yaml - does node framework start the health check server automatically? If not, proof data handler should spawn it. |
Never mind. Proof data handler has the health server, so we will integrate with it properly. ✅ |
Closing as it turned out there is already a health check endpoint we can reuse. |
What ❔
Add
/health
endpoint to theproof_data_handler
introduced in eca98cc (#1993).Why ❔
The DevOps team asked for a health check endpoint so the in-cluster load balancer can use it. Details: https://matter-labs-workspace.slack.com/archives/C05MZ0ZUB6Z/p1718801741282109?thread_ts=1718191882.611349&cid=C05MZ0ZUB6Z
Checklist
zk fmt
andzk lint
.zk spellcheck
.