-
Epic
-
Resolution: Unresolved
-
Critical
-
None
-
vm-workloads-perserving-staticIPs-cnv-tracker
-
77
-
-
Green
-
In Progress
-
33% To Do, 6% In Progress, 61% Done
-
dev-ready, doc-ready, qe-ready, ux-ready
-
Feature
-
-
Proposed
-
Critical
Goal
CNV tracker for https://issues.redhat.com/browse/CORENET-6312
Allow import of VMs connected to an overlay network. This includes:
- Specifying the IP address of the VM for OVNK to use (but not assign) via persistent IP or some other mechanism
- Detect/expose the MAC for the VM to be configured in OVNK for the VM
- When creating the UDN, be able to specify the gateway IP address, so the migrated VM can keep the same default route.
- 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
- clones
-
CNV-4600 CNV Epic Template
-
- New
-
- is cloned by
-
CNV-69307 [4.20.z GA] Allow import of VMs connected to an overlay network
-
- New
-
- is depended on by
-
CNV-69307 [4.20.z GA] Allow import of VMs connected to an overlay network
-
- New
-
-
CNV-62188 Scale tests on egress/ingress(unNATed)
-
- New
-
-
MTV-2857 TP: Preserve static IP addresses in UDN networks
-
- In Progress
-
- is duplicated by
-
MTV-3539 [QE] Preserve static IPv4 addresses in UDN networks
-
- Closed
-
- is related to
-
MTV-1369 Support mapping to primary user-defined networks and import of IPs
-
- In Progress
-
-
CORENET-6025 TechPreview: Support for egress/ingress(unNATed using BGP) for VMs on L2 CUDNs: using IPAMClaims (day0 IPs only no changes on day2)
-
- Testing
-
-
MTV-2999 [Doc] Support mapping to primary user-defined networks
-
- Testing
-
- relates to
-
MTV-2857 TP: Preserve static IP addresses in UDN networks
-
- In Progress
-
1.
|
upstream roadmap issue |
|
Closed | |
Unassigned |
2.
|
upstream design |
|
Closed | |
Miguel Duarte de Mora Barroso |
3.
|
upstream documentation |
|
New | |
Unassigned |
4.
|
upgrade consideration |
|
New | |
Unassigned |
5.
|
CEE/PX summary presentation |
|
Closed | |
Unassigned |
6.
|
test plans in polarion |
|
New | |
Unassigned |
7.
|
automated tests |
|
New | |
Unassigned |
8.
|
downstream documentation merged |
|
New | |
Unassigned |