Skip to content

deployment: add liveness probe to hybrid environment overlays#14191

Open
nimrod-starkware wants to merge 1 commit into
05-25-deployment_add_readiness_probe_to_hybrid_environment_overlaysfrom
05-25-deployment_add_liveness_probe_to_hybrid_environment_overlays
Open

deployment: add liveness probe to hybrid environment overlays#14191
nimrod-starkware wants to merge 1 commit into
05-25-deployment_add_readiness_probe_to_hybrid_environment_overlaysfrom
05-25-deployment_add_liveness_probe_to_hybrid_environment_overlays

Conversation

@nimrod-starkware
Copy link
Copy Markdown
Contributor

@nimrod-starkware nimrod-starkware commented May 25, 2026

@reviewable-StarkWare
Copy link
Copy Markdown

This change is Reviewable

@cursor
Copy link
Copy Markdown

cursor Bot commented May 25, 2026

PR Summary

Low Risk
Operational Kubernetes probe config only; no application logic or secrets, with restarts only after repeated failed health checks.

Overview
Enables Kubernetes liveness checks for hybrid sequencer deployments by adding a shared livenessProbe block to the mainnet, sepolia-alpha, and sepolia-integration common.yaml overlays.

Each overlay turns the probe on against /monitoring/alive (same path as the existing startup probe), with 10s period, 5 consecutive failures before restart, and a 3s timeout. Readiness (/monitoring/ready) is unchanged; this only adds restart behavior when the process stays up but stops responding as alive.

Reviewed by Cursor Bugbot for commit 0a4630d. Bugbot is set up for automated code reviews on this repo. Configure here.

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 this pull request may close these issues.

2 participants