Epic Goal

• Make kubernetes-nmstate a fully supported component on vSphere. This primarily means it will need to be documented and tested on this platform.

Why is this important?

• Customers want to have a declarative interface to configure the networking on their clusters on platforms other than baremetal.

Scenarios

1. As a deployer on vsphere, I want to customize networking settings like DNS servers/search domains, VLANS, bridges, and bonds using a declarative interface.

Acceptance Criteria

• Works with vSphere
• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.

Dependencies (internal and external)

1. We will need assistance from the other on-prem platform teams since the baremetal developers and QE may not have access to the necessary environments.

Previous Work (Optional):

1. https://issues.redhat.com/browse/SDN-2215

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement N/A
• DEV - Upstream code and tests merged: N/A
• DEV - Upstream documentation merged: N/A
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: https://polarion.engineering.redhat.com/polarion/#/project/OSE/testrun?id=20220909-0742
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: https://github.com/openshift/openshift-docs/pull/51249