Feature Overview (aka. Goal Summary)  

Support the ability to configure UPI Installed Openshift Clusters to be enabled in either single stack IPv6 or dual stack IPv4/IPv6 (additionally to the current default IPv4)

Goals (aka. expected user outcomes)

As per our production documentation[1], dualstack(IPv4/IPv6) configuration is supported in vSphere IPI. Organizations using UPI installation want to have the feature of installing either single stack IPV6 or dualstack (IPv4/IPv6) enabled on their clusters.

[1] https://docs.openshift.com/container-platform/4.16/networking/ovn_kubernetes_network_provider/about-ovn-kubernetes.html

Requirements (aka. Acceptance Criteria):

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):

NA

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

OpenShift supports IPI installations with IPv6 dual-stack on bare metal deployments since version 4.8.
Customer are requesting support for UPI installations with single IPv6 and dual-stack on deployments 

Customer Considerations

Customer with critical application are utilizing devices configured with either IPv6 or dual stack (IPv6/IPv4) more often than previously. As the number of users using IPv6 are increasing, customers are looking to support UPI installations to support IPv6 single stack and dual-stack. 

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>