Support for NVSwitch in Shared NVSwitch Virtualization Model

I'm running a Kata containers k8s cluster with HGX H100 servers. I want to run fabricmanager in the Shared NVSwitch Virtualization Mode whereby a service VM runs fabricmanager to set up the NVSwitch partitions. This could be done by making a Kata daemonset that only runs fabricmanager and has the NVSwitch devices passed through. However this requires k8s to know about NVSwitch devices. I would like to ask if there are any plans to support this, and also whether you'd be open to contributions to get this supported.

This has tie-ins with the CoCo work already released in GPU Operator: https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/confidential-containers-deploy.html and another PR just recently opened in GPU Operator that allows further configuration of fabricmanager.

CC @zvonkok @fidencio

Start by reviewing the repository's device-plugin implementation and the linked Kata Containers and GPU Operator documentation and PR. Determine how Kubernetes should discover and pass through NVSwitch devices for Shared NVSwitch Virtualization Mode, then confirm the expected daemonset and fabricmanager workflow with maintainers. Done requires an agreed implementation scope and validation path.