-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
multi-networkpolicy-nft-support
-
Product / Portfolio Work
-
100% To Do, 0% In Progress, 0% Done
-
False
-
-
False
-
XL
-
None
-
None
-
0
Template:
Networking Definition of Planned
Epic Template descriptions and documentation
Epic Goal
Support nftables backend in multi-networkpolicy
-...
Why is this important?
In RHEL10, iptables-nft will be removed. Once iptables-nft removed, then current multi-networkpolicy does not work because multi-networkpolicy uses iptables-nft for backend. This EPIC changes multi-networkpolicy to support nftables backends.
-…
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.
...
- is duplicated by
-
CORENET-6264 [TRACKER] Transition Multi-network Policy away from iptables (Tech Preview)
-
- Closed
-
- relates to
-
OCPSTRAT-940 Deprecation of iptables in OpenShift [Phase 2]
-
- New
-
-
OCPSTRAT-873 Deprecation of iptables in OpenShift [Phase 1]
-
- Closed
-