Template:

Networking Definition of Planned

Epic Template descriptions and documentation 

Epic Goal

• Replace the current OVN-based service proxy in ovn-kubernetes with the new upstream nftables mode of kube-proxy.

Why is this important?

• The existing Service proxy code in ovn-kubernetes is one of the remaining places that does not scale well to large clusters.
• Using upstream code for Service proxying means more code maintenance shared with all of upstream, and less OCP-specific/OVN-K-specific code to maintain
• In particular, it means that we will automatically get implementations of new Service features for free, rather than having to separately implement them ourselves.

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.

...