Goal

The default VMI network binds a pod network interface to a VMI using NAT. This method is called "Masquerade"

Masquerade behaves differently than many networking solutions people have encountered in previous VM management platforms. The IP the guest OS sees isn't reachable by any other endpoint in the cluster, which breaks a pretty basic assumption that holds true for other VM platforms.

The goal of this epic is to provide a new binding suitable for the pod network where the guest would carry the Pod IP. This would be a replacement for the unsupportable bridge binding for pod network and enable applications that identify themselves by IP of their hosts.

User Stories

• As a developer,
  I want my VM to see its public PodIP,
  so it can use it for its own identification.
• As a developer,
  I want my VM to have the same IP internally and externally,
  so the is no mismatch.
• As a developer,
  I want the CNV pod network to resemble usual cloud network setup,
  so I can install OCP over CNV and have my VMs reachable by infrastructure routers and services

Non-Requirements

• It is not required for the VM to preserve its IP. It is acceptable if it changes after live migration or reboot.

Notes

• The requirement is outlined in https://docs.google.com/document/d/1FeInETvW-ZY9kEtoiopD9jAU54WHKHxupiE82Ywzh7w/edit#heading=h.rkmyri2mqi3z
• This is only for the Pod network. On multus networks, we still want to use bridge binding to provide L2 connection.

Owners

Done Checklist