What problem does it solve? Deploying the NVIDIA Network Operator involves many manual steps: generating Helm values, creating NicClusterPolicy and network CRDs, configuring SR-IOV node pools, and verifying RDMA networking. This Skill guides the full pipeline from configuration generation through Helm install and post-deploy verification, reducing misconfiguration risk. ## Core Features & Use Cases - Config Generation: Runs mk-config.sh to produce values.yaml, NicClusterPolicy.yaml, network CRDs, IPAM pools, and SR-IOV node pool configs from a platform-specific global_ops_user.cfg. - Guided Deployment: Walks through use case selection, dry-run config review (CREATE_CONFIG_ONLY=1), and actual Helm/kubectl deployment (CREATE_CONFIG_ONLY=0). - Troubleshooting & Verification: Provides checks for common failures (missing config, wrong chart version, SR-IOV sync delays, IP pool exhaustion) plus verification commands like getnetwork.sh, checksriovstate.sh, and checkipam.sh. - Use Case: A cluster admin needs RDMA networking for GPU workloads on a DGX B200 cluster. The Skill guides copying the platform config, generating YAML, deploying the operator, and confirming SR-IOV VFs are synced. ## Quick Start Deploy the NVIDIA Network Operator to my Kubernetes cluster using netop-tools with the sriovnet_rdma use case.