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

Update Health Check Endpoints for Liveness and Readiness #264

Open
alainncls opened this issue Dec 5, 2024 · 0 comments · Fixed by #263
Open

Update Health Check Endpoints for Liveness and Readiness #264

alainncls opened this issue Dec 5, 2024 · 0 comments · Fixed by #263
Assignees

Comments

@alainncls
Copy link
Collaborator

alainncls commented Dec 5, 2024

Description:

The current /health endpoint is used for both liveness and readiness probes, which is not following best practices. This task involves:

  1. Creating a new /live endpoint that always returns a 200 status for the liveness probe.
  2. Adjusting the /health endpoint to focus exclusively on readiness checks, ensuring it validates dependencies (e.g., Infura).
  3. Renaming the /health endpoint to /ready
  4. Updating Kubernetes configurations to correctly use /live for liveness and /health for readiness.

Acceptance Criteria:

  • A new /live endpoint is created, always returning 200.
  • The /ready endpoint performs only readiness checks and reflects dependency states.
  • Kubernetes configurations are updated to:
    • Use /live for liveness probes.
    • Use /ready for readiness probes.
@alainncls alainncls self-assigned this Dec 5, 2024
@alainncls alainncls changed the title Split healthcheck and readiness endpoints Update Health Check Endpoints for Liveness and Readiness Dec 6, 2024
@alainncls alainncls reopened this Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant