deployment: move network and consensus ports to hybrid environment overlays

[nimrod-starkware]

Corresponding devops PR: https://github.com/starkware-industries/sequencer-devops/pull/706

[reviewable-StarkWare]

This change is 

[nimrod-starkware]

• deployment: define common env #14196 : 2 dependent PRs (#14209 , #14215 )
• deployment: add gcp pod monitoring to hybrid environment overlays #14192
• 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
• deployment: add monitoring endpoint port to hybrid environment overlays #14187
• deployment: add service ports to hybrid environment overlays #14185
• deployment: move network and consensus ports to hybrid environment overlays #14183 👈 (View in Graphite)
• deployment: add component ports and urls to hybrid environment overlays #14181
• deployment: add recorder_url to hybrid environment overlays #14180
• deployment: add starknet_url to hybrid environment overlays #14179
• main

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

[cursor]

PR Summary

Medium Risk
Production hybrid deployments depend on correct listener ports for consensus and state sync; misconfiguration could break node connectivity until rolled back.

Overview
Adds hybrid core service overlay port and networking settings for mainnet, sepolia-alpha, and sepolia-integration so consensus, state sync, batcher/class storage readers, and RPC listen addresses are defined per environment instead of relying on shared defaults.

Each overlay now sets consensus_manager_config.network_config.port 53080, batcher/class storage reader ports 55011 / 55210, and state sync P2P port 55010, RPC 8090, and storage reader 55012. Mainnet enables state sync network_config (#is_none: false); sepolia-alpha and sepolia-integration keep state sync network config disabled (#is_none: true) while still pinning the port values for when devops wires services up.

This matches the paired devops work to expose the same ports in Kubernetes.

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

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 7b0b0a0. Configure here.}

[dorimedini-starkware]

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

---

a discussion (no related file):
general question: is there a config that is common for all networks? because all these values are identical.. is this a planned feature? part of the jsonnet migration?

[nimrod-starkware]

@nimrod-starkware made 2 comments.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on dorimedini-starkware, idan-starkware, and matanl-starkware).

---

a discussion (no related file):

Previously, dorimedini-starkware wrote…

general question: is there a config that is common for all networks? because all these values are identical.. is this a planned feature? part of the jsonnet migration?

Yes, see this.
It's in this stack...

[dorimedini-starkware]

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