Advertise KubeVirt VM host routes per node - #139
aswinsuryan wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: LGTM mode |
|
Skipping CI for Draft Pull Request. |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Advanced Run ID: Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aswinsuryan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
4257476 to
8a4f0a3
Compare
A shared CUDN prefix can be advertised by multiple BGP workers even though an L2 UDN VM is hosted by only one node. AWS may send return traffic to a different worker from the one used by the VM's outgoing traffic. The return worker's ENI has no connection-tracking state for the VM-initiated flow, so its security group can reject the reply unless the VM's ephemeral destination port is explicitly allowed inbound. Track running VMIs and advertise each guest address as a node-pinned /32 or /128 route from its hosting worker. Reconcile routes during VM start, stop, and migration, and exclude these configurations from OVN RouteAdvertisements. Signed-off-by: Aswin Suryanarayanan <asuryana@redhat.com> Co-authored-by: Codex <codex@openai.com>
8a4f0a3 to
5e50fad
Compare
|
@aswinsuryan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
A shared CUDN prefix can be advertised by multiple BGP workers even though an L2 UDN VM is hosted by only one node. AWS may send return traffic to a different worker from the one used by the VM's outgoing traffic.
The return worker's ENI has no connection-tracking state for the VM-initiated flow, so its security group can reject the reply unless the VM's ephemeral destination port is explicitly allowed inbound.
Track running VMIs and advertise each guest address as a node-pinned /32 or /128 route from its hosting worker. Reconcile routes during VM start, stop, and migration, and exclude these configurations from OVN RouteAdvertisements.