-
Epic
-
Resolution: Unresolved
-
Undefined
-
None
-
None
-
None
-
NetworkPolicy nftables
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-940 - Deprecation of iptables in OpenShift [Phase 2]
-
-
100% To Do, 0% In Progress, 0% Done
-
XL
-
---
-
0
-
0
Template:
Networking Definition of Planned
Epic Template descriptions and documentation
Epic Goal
- Implement NetworkPolicy and AdminNetworkPolicy in nftables, in an upstream project with no dependencies on OCP
- Use this in ovn-kubernetes
Why is this important?
- Providing a standard upstream implementation of NetworkPolicy will be useful to many Kubernetes users, and using that in OCP will help us by letting us share maintenance with upstream.
- Providing another implementation of AdminNetworkPolicy will help to push that forward towards full standardization.
- This could also be used as a basis for porting MultiNetworkPolicy away from iptables
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.
...