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]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• deployment: define common env #14196
• 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

Low Risk
Deployment-only port and network toggles in YAML overlays; misconfiguration could affect connectivity but does not change application logic.

Overview
Adds hybrid core service overlay keys for consensus, batcher/class storage readers, and state sync networking across mainnet, sepolia-alpha, and sepolia-integration.

Each environment now sets consensus_manager_config.network_config.port to 53080, storage reader ports (55011 / 55210), and state sync ports (55010, 8090, 55012). Mainnet enables state sync P2P via state_sync_config.static_config.network_config.#is_none: false; the two Sepolia overlays keep P2P disabled (#is_none: true) while still defining the port values.

^{Reviewed by Cursor Bugbot for commit 7b0b0a0. 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.}

[cursor]

Port 55012 conflict between proof_manager and state_sync storage reader

High Severity

The newly added state_sync_config.static_config.storage_reader_server_static_config.port: 55012 conflicts with the pre-existing components.proof_manager.port: 55012. Both create TCP listeners on port 55012 within the same core service pod — the proof_manager creates a gRPC remote server bound to 0.0.0.0:55012, and the storage reader server creates an HTTP server also on 0.0.0.0:55012. This will cause an "address already in use" error at startup in all three environments.

Additional Locations (2)

• deployments/sequencer/configs/overlays/hybrid/sepolia-alpha/services/core.yaml#L59-L60
• deployments/sequencer/configs/overlays/hybrid/sepolia-integration/services/core.yaml#L59-L60

 

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