Feat: Add DpuNetwork CR, Per-network device pools and Accelerated NF support

[alkama-hasan]

This PR introduces a cluster-scoped DpuNetwork CRD (config.openshift.io) with a controller and device plugin manager for per-network DPU resource management and covers e2e deployment of Accelerated NF.

Changes

• DpuNetwork API: nodeSelector, dpuSelector (vfId range support), isAccelerated; status with resourceName, selectedVFs, and conditions.
• Controller: writes per-network entries to dpu-device-plugin-config ConfigMap, creates a NAD per DpuNetwork, manages finalizer for cleanup on delete.
• Device Plugin Manager: polls ConfigMap to start/stop per-network and accelerated device plugins; gracefully restarts default plugin when all networks are removed.
• Accelerated NF Mode: per-VF CreateNetworkFunction/DeleteNetworkFunction with bridgeID plumbed through CNI config, BridgePort, and NF APIs.
• Device Recovery: recovers orphaned VF representors on namespace teardown and graceful daemon shutdown via releaseNfDevices and recoverOrphanedDevice.
• CNI Config: added bridgeID and isAccelerated fields to NetConf; BridgePort now uses bridgeID instead of hardcoded vf+2.
• VendorPlugin Interface: extended with bridgeID parameter and SetDpuNetworkConfig RPC; GrpcPlugin wires DpuNetworkConfigServiceClient.
• Marvell VSP: implements SetDpuNetworkConfig gRPC to toggle accelerated mode and report accelerated devices.
• Host/DPU Side Managers: K8s client creation for config-driven device plugin registration with fallback on failure.
• PathManager: unique socket paths per network (dpuNet-<name>.sock).
• RBAC: controller permissions for dpunetworks, ConfigMaps, NADs; daemon role updated with ConfigMap access.
• CRD/Examples: OpenAPI schema, print columns, dpunetwork-net1.yaml, dpunetwork-net2.yaml, host-pod.yaml, nf-pod.yaml.

[openshift-ci]

Hi @alkama-hasan. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[wizhaoredhat]

/approve

[wizhaoredhat]

/ok-to-test

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alkama-hasan, wizhaoredhat

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [wizhaoredhat]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[alkama-hasan]

/retest

[alkama-hasan]

/retest

[alkama-hasan]

/retest

[alkama-hasan]

/test make-test

[openshift-ci]

@alkama-hasan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/verify-deps	be1c641	link	true	/test verify-deps
ci/prow/make-vendor-check	be1c641	link	true	/test make-vendor-check
ci/prow/make-e2e-test-marvell	be1c641	link	true	/test make-e2e-test-marvell
ci/prow/make-test	be1c641	link	true	/test make-test

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.