Template:

Networking Definition of Planned

Epic Template descriptions and documentation 

Epic Goal

• Determine all of the components that are part of "Bare Metal networking" that make use of iptables
• Come up with a plan to switch them over to nftables, eBPF, or some other non-iptables technology over the next several OCP releases.
• (This epic does not cover the actual implementation of that plan, which may happen over multiple later releases.)

Why is this important?

• iptables is deprecated in RHEL 9 and will no longer be present in RHEL 10 (likely 2-3 years from now). We need to make sure we have a plan to no longer be using it by then.

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.

...