Template:

Networking Definition of Planned

Epic Template descriptions and documentation

Epic Goal

The NVIDIA DPF solution requires stateless network policy in order to offload RDMA traffic without conntrack on the DPU becoming overwhelmed. The only way to support this is with the Stateless Network Policy feature in OVN Kubernetes.

This feature is, however, not currently supported and the API for it has not been submitted for API review.

We believe the correct way for this feature to become generally available is for it to be discussed in the k8s network policy group and perhaps folded into an existing NetworkPolicy API object instead of creating a new one.

Why is this important?{}

The NVIDIA DPF solution is timing sensitive and is targetted for GA in 4.22.
Therefore we must provide a solution in the interim.

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)
  1. Please use the “Discussion Needed: Service Delivery Architecture Overview” checkbox to facilitate the conversation with SD Architects. The SD architecture team monitors this checkbox which should then spur the conversation between SD and epic stakeholders. Once the conversation has occurred, uncheck the “Discussion Needed: Service Delivery Architecture Overview” checkbox and record the outcome of the discussion in the epic description here.
  2. The guidance here is that unless it is very clear that your epic doesn’t have any managed services impact, default to use the Discussion Needed checkbox to facilitate that conversation.

Additional information on each of the above items can be found here: Networking Definition of Planned

Acceptance Criteria

• Upstream CI - MUST be running successfully with tests automated
• Downstream CI - MUST run with this feature enabled
• Release Technical Enablement - Provide necessary release enablement
  details and documents.

Dependencies (internal and external)

1. External dependency on NVIDIA to provide upstream tests in ovn-kubernetes

Previous Work (Optional):

Open questions::

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>