Multi nic support with SR-IOV

[tamilmani1989]

The requirement is to allocate and attach a secondary SR-IOV NIC to a pod. The DRA driver discovers secondary SR-IOV NIC resources on the node and publishes them as ResourceSlice objects. Users then request the required secondary NICs for their pods through a ResourceClaim.

During pod creation, kubelet invokes DRA via PrepareResource, passing the pod and assigned NIC details. As part of RunPodSandbox, the NRI hook is triggered and is responsible for moving the corresponding secondary NIC into the pod’s network namespace. Finally, DRA/NRI must configure the necessary routes and policy rules so that traffic ingressing on the secondary NIC also egresses through the same interface.

[aojea]

Thanks @tamilmani1989 I think about this repo as an incubator of drivers and idea, that does not mean we will have a lower bar than projects like DRANET, same or higher, and also eventually some features can also be imported on DRANET.

Some questions:

The DRA driver discovers secondary SR-IOV NIC resources on the node

This is only about network devices and virtual function?

Finally, DRA/NRI must configure the necessary routes and policy rules so that traffic ingressing on the secondary NIC also egresses through the same interface.

How is this UX, how the routes and rules are passed to the driver? Via configuration or.are discovered, or both?

To ensure the design meets the actual needs of the community, I’d like to step back and look at the User Story.

Could you describe the high-level use case without the implementation details? Specifically:

• The 'Who': Who is the end-user here? (e.g., a Telco admin, a High-Performance Computing developer?)

• The 'What': What is the user actually defining in their Pod spec or ResourceClaim?

• The 'Why': What problem does this solve for them? Is it for multi-homing for security isolation?

Understanding the UX (how the user expects to request and interact with these NICs) will help us determine if the routing and policy rules should be automated by the driver or configurable by the user and other technical designs.