Epic Goal

Backport the fix for IPv6 single stack in kubernetes-nmstate to 4.12

Why is this important?

Significant customers want to use single stack IPv6 in 4.12 and also want to be able to use kubernetes-nmstate.

Planning Done Checklist

The following items must be completed on the Epic prior to moving the Epic from Planning to the ToDo status

• Priority+ is set by engineering
• Epic must be Linked to a +Parent Feature
• Target version+ must be set
• Assignee+ must be set
• (Enhancement Proposal is Implementable
• (No outstanding questions about major work breakdown
• (Are all Stakeholders known? Have they all been notified about this item?
• Does this epic affect SD? {}Have they been notified{+}? (View plan definition for current suggested assignee)

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• The single stack IPv6 fix commit from upstream must be backported to 4.12 (and also 4.13 since we can't skip releases).
• QE must verify that the operator functions correctly in single stack IPv6 clusters after the backport.

Dependencies (internal and external)

1. The primary reason we are tracking this with an epic and not just a bug is that clearly we were not testing single stack IPv6 with kubernetes-nmstate in 4.12 so we are going to need QE involvement to verify that the fix actually works. Since this may be non-trivial (we've found that adding ci for single stack IPv6 in 4.14 has been more difficult than expected) we want to make sure everyone is onboard with the plan before we proceed.