Feature Overview (aka. Goal Summary)  

Test and validate MicroShift is working correctly in IPV6 environments.

Goals (aka. expected user outcomes)

1. Dualstack: Users can run MicroShift and their workload in IP V4/V6 dual stack environments, meaning ingress and egress traffic can be on V4 or V6 traffic, even mixed and parallel.
2. Single-V6 stack: User can run MicroShift and their workload in pure IPV6 only environments.

Requirements (aka. Acceptance Criteria):

1. Both V4 and V6 CIDR for cluster/pod and service networks need to be configurable. 
2. Ingress Controller needs to handle V6 traffic correctly

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

Questions to Answer (Optional):

Out of Scope

Converting clusters to/from single/dualstack environments is initially out of scope and not supported. Network stack must be configured before initial boot. 

Background

We see more and more adaption of IP V6, hence we have to ensure MicroShift is ready for this.

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Documentation Considerations

MicroShift networking documentation needs to be augmented by examples on how to config dualstack V4V6 and singlestack V6 only.

Interoperability Considerations

This relies on ovn-k implementation from OpenShift, but no special integration / testing expected.