deployment: add startup probe to hybrid environment overlays

[nimrod-starkware]

Cross-repo PR: https://github.com/starkware-industries/sequencer-devops/pull/713

Cross-repo PR: https://github.com/starkware-industries/sequencer-devops/pull/713

[reviewable-StarkWare]

This change is 

[nimrod-starkware]

• deployment: add gcp pod monitoring to hybrid environment overlays #14192 : 2 dependent PRs (#14196 , #14242 )
• deployment: add liveness probe to hybrid environment overlays #14191
• deployment: add readiness probe to hybrid environment overlays #14190
• deployment: add startup probe to hybrid environment overlays #14188 👈 (View in Graphite)
• deployment: add monitoring endpoint port to hybrid environment overlays #14187
• main-v0.14.3

This stack of pull requests is managed by Graphite. Learn more about stacking.

[cursor]

PR Summary

Low Risk
Operational-only Kubernetes probe settings; no application logic, auth, or chain config changes beyond rollout behavior during pod startup.

Overview
Enables Kubernetes startup probes on hybrid sequencer deployments for mainnet, sepolia-alpha, and sepolia-integration by adding the same startupProbe block to each environment’s common.yaml overlay.

Pods will not be treated as failed during slow boot: the probe calls /monitoring/alive on the existing monitoring port (8082), with 5s intervals, 2s timeouts, and up to 30 failures (~2.5 minutes max startup) before Kubernetes gives up. This overrides the layout default of an empty startupProbe: {} for these networks only.

^{Reviewed by Cursor Bugbot for commit e507038. Bugbot is set up for automated code reviews on this repo. Configure here.}

[dorimedini-starkware]

@dorimedini-starkware reviewed 3 files and all commit messages, and made 1 comment.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on idan-starkware, matanl-starkware, and nimrod-starkware).

---

deployments/sequencer/configs/overlays/hybrid/mainnet/common.yaml line 29 at r1 (raw file):

  failureThreshold: 30
  periodSeconds: 5
  timeoutSeconds: 2

I notice these are not alphabetical, this yml is not auto-generated, right?
can you add a test that verifies all manual ymls are sorted? (since this is under the deployments directory, I guess you can do it in python)
not blocking this PR - this is a side quest. it will make reviewing easier (when reviewing this PR i would like to remember "1,30,5,2", and the rely on alphabetical order to make sure the same values go to the same fields)

Code quote:

startupProbe:
  enabled: true
  path: /monitoring/alive
  successThreshold: 1
  failureThreshold: 30
  periodSeconds: 5
  timeoutSeconds: 2

[dorimedini-starkware]

@dorimedini-starkware reviewed 3 files and all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on idan-starkware, matanl-starkware, and nimrod-starkware).

[graphite-app]

Merge activity

• May 28, 9:10 AM UTC: Graphite rebased this pull request, because this pull request is set to merge when ready.

[dorimedini-starkware]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on idan-starkware, matanl-starkware, and nimrod-starkware).

[nimrod-starkware]

@nimrod-starkware resolved 1 discussion.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on idan-starkware and matanl-starkware).