Phase 3: OpNode#2
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
… service discovery details for L2 connectivity, and refactor getSequencerEndpoint function in statefulset.go to support dynamic endpoint resolution. This improves configuration management and clarifies the separation of L1 and L2 responsibilities.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…nerated and user-provided private keys. Update volume and mount configurations to reflect the new logic for determining secret names based on key management method.
…C port configuration.
…atus fields during updates, improving race condition handling.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…after secrets and StatefulSet readiness, improving status management and logging for errors during updates.
There was a problem hiding this comment.
Bug: Replica Nodes Fail to Connect Due to Incorrect Endpoint
The getSequencerEndpoint function incorrectly constructs the sequencer endpoint for replica nodes. It hardcodes the HTTP port to 8545, ignoring the configurable opNode.Spec.OpGeth.Networking.HTTP.Port. Additionally, it assumes a sequencer service name of {network.Name}-sequencer, while OpNode services are actually named after the opNode.Name. This results in replica nodes failing to connect to the sequencer.
pkg/resources/statefulset.go#L514-L525
Was this report helpful? Give feedback by reacting with 👍 or 👎
2 participants
No description provided.