deployment: add component ports and urls to hybrid environment overlays#14181
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
924d0ed to
1c33c4c
Compare
0e34ea9 to
1bc33cd
Compare
PR SummaryMedium Risk Overview Each service overlay only gets the component endpoints that process needs (e.g. core gets the full cross-service map; committer only batcher + committer; sierra-compiler only sierra_compiler). Host/port values are the same across all three environments; only existing env-specific settings (L1 addresses, cache sizes, etc.) stay different. This moves hybrid inter-service discovery into the sequencer repo overlays (paired with removal of the same keys from sequencer-devops). Reviewed by Cursor Bugbot for commit 1c33c4c. Bugbot is set up for automated code reviews on this repo. Configure here. |
dorimedini-starkware
left a comment
There was a problem hiding this comment.
@dorimedini-starkware reviewed 18 files and all commit messages.
Reviewable status:complete! all files reviewed, all discussions resolved (waiting on idan-starkware and matanl-starkware).

Add
components.*port and URL entries to each production environment's service overlays (core, l1, gateway, mempool, committer, sierra-compiler) for mainnet, sepolia-alpha, and sepolia-integration.Values are identical across all three environments.
Corresponding devops PR (removes the same keys from the devops overlays): starkware-industries/sequencer-devops#703