Uploaded image for project: 'OpenShift Virtualization'
  1. OpenShift Virtualization
  2. CNV-61227

Allow import of VMs connected to an overlay network

XMLWordPrintable

    •  vm-workloads-perserving-staticIPs-cnv-tracker
    • 77
    • Hide
      • MTV is able to request a specific IP for a primary UDN interface
      • Test plan for both the IP request and ingress/egress
      • Test automation, at least for the IP request
      • MTV integrates with this feature, exposing it on their UI and docs
      • No CNV docs, just a release note - MTV is the one exposing this feature to the customer and should document the details
      • No CNV UXD - MTV is exposing this option on their UI
      Show
      MTV is able to request a specific IP for a primary UDN interface Test plan for both the IP request and ingress/egress Test automation, at least for the IP request MTV integrates with this feature, exposing it on their UI and docs No CNV docs, just a release note - MTV is the one exposing this feature to the customer and should document the details No CNV UXD - MTV is exposing this option on their UI
    • Green
    • In Progress
    • 33% To Do, 6% In Progress, 61% Done
    • dev-ready, doc-ready, qe-ready, ux-ready
    • Feature
    • Hide

      2025-08-25:
      QE learning how to work with MTV. Patches still stuck in the pipeline trying to get D/S...

      Show
      2025-08-25: QE learning how to work with MTV. Patches still stuck in the pipeline trying to get D/S...
    • Proposed
    • Critical

      Goal

      CNV tracker for https://issues.redhat.com/browse/CORENET-6312

      Allow import of VMs connected to an overlay network. This includes:

      1. Specifying the IP address of the VM for OVNK to use (but not assign) via persistent IP or some other mechanism
      2. Detect/expose the MAC for the VM to be configured in OVNK for the VM
      3. When creating the UDN, be able to specify the gateway IP address, so the migrated VM can keep the same default route.
      4. When creating the UDN, allow excludeSubnets to be used with L2 UDNs to ensure OVNK does not use an IP address from the range that VMs have already been assigned outside of the cluster.

      User Stories

      • As the owner of a VM running in a traditional virtualization platform, I want to import said VM - whose IPs were statically configured - into Kubernetes, attaching it to an overlay network. I want to ingress/egress using the same IP address (the one assgined to the VM).
      • As the owner of a VM running in a traditional virtualization platform, I want to import said VM into Kubernetes, attaching it to an overlay network. I want to have managed IPs for my VMs, since that feature was already available in my previous platform.
      • As the owner of a VM running in a traditional virtualization platform, I want to import said VM into Kubernetes, attaching it to an overlay network. I want to be able to consume Kubernetes features like network policies, and services, to benefit from the Kubernetes experience.

      Non-Requirements

      •  

      Notes

      • Any additional details or decisions made/needed

              mduarted@redhat.com Miguel Duarte de Mora Barroso
              mduarted@redhat.com Miguel Duarte de Mora Barroso
              Yossi Segev Yossi Segev
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: