Skip to content
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

Liveness endpoint #538

Closed
jframe opened this issue Mar 22, 2022 · 0 comments · Fixed by #610
Closed

Liveness endpoint #538

jframe opened this issue Mar 22, 2022 · 0 comments · Fixed by #610
Assignees
Labels
TeamCerberus Under active development by TeamCerberus @Consensys

Comments

@jframe
Copy link
Contributor

jframe commented Mar 22, 2022

Add a liveliness endpoint to Web3Signer so that infrastructure can know when web3signer is up and running and able to accept requests. This would it easier for users that have Web3Signer in kubernetes and simplify their deployement.

Tasks

  • Investigate format for the health and liveliness endpoints
  • Determine what endpoints we should have to integrate with kubernetes and to allow for easier deployment
@jframe jframe added the TeamCerberus Under active development by TeamCerberus @Consensys label Mar 22, 2022
@wcgcyx wcgcyx self-assigned this Jul 5, 2022
@wcgcyx wcgcyx mentioned this issue Jul 11, 2022
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TeamCerberus Under active development by TeamCerberus @Consensys
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants