Feature Overview (aka. Goal Summary)  

Add best practices of installing/upgrading and migrating to OpenShift clusters with OVN Kubernetes on vSphere with multi-NIC configuration. 

Goals (aka. expected user outcomes)

Customers should have visibility into the best practices for the install/upgrade/migrate scenarios, to include avoidance of issues as highlighted here.

Requirements (aka. Acceptance Criteria):

We believe the procedure highlighted in the (currently unpublished) KCS article highlights the proper considerations for not just installations, but also for upgrade and migration scenarios. This, however, requires QE testing and documentation (add it to our product documentation)

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

• Initially, vSphere UPI

Questions to Answer (Optional):

Out of Scope

Background

When installing OpenShift to a vSphere platform with OVN networking when the instances have more than one NIC, the installation will fail, reporting a failure of the bootstrap to complete. The resolution requires the customer to consider adding the internal and external subnet CIDRs, or network names, to their vSphere cloud controller manager configuration, as per the KCS article.
The Kubernetes vSphere Cloud Provider documentation contains more detail about this in the Nodes section of the vSphere Cloud Config Spec page.

Customer Considerations

Documentation Considerations

• The product documentation should highlight the consideration articulated in the KCS article.
• Testing and documenation priority is for installations (UPI), first, followed by upgrade and migrations.
• We will need to eventually enhance our documentation to include other installation types, but that is less of a priority at the moment.

Interoperability Considerations