Template:

Networking Definition of Planned

Epic Template descriptions and documentation 

Epic Goal

• Switch kube-proxy in openshift-sdn from iptables mode to nftables
• Replace the random bits of iptables glue in openshift-sdn with exactly equivalent nftables versions

Why is this important?

• iptables will not be supported in RHEL 10, so we need to replace all uses of it in OCP with nftables. See OCPSTRAT-873.
• Once the new nftables kube-proxy mode is used in ovn-kubernetes (SDN-4110), using it in openshift-sdn as well will mean there is less openshift-sdn-specific code to maintain.

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

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

...

Dependencies (internal and external)

1.

...