メニュー
Upgrade NVIDIA Network Operator to a new version. Use when changing NETOP_VERSION, running upgrade-network-operator.sh, migrating between operator versions, handling CRD schema changes, or rolling back a failed upgrade.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Configure netop-tools for a specific hardware platform and use case. Use when setting up global_ops_user.cfg, choosing a use case (sriovnet_rdma, sriovibnet_rdma, hostdev, ipoib, macvlan), selecting IPAM type, configuring NETOP_NETLIST device list, setting feature flags, or switching between platforms (DGX, Dell, Lenovo, OCI, SuperMicro).
Deploy NVIDIA Network Operator to a Kubernetes cluster via netop-tools. Use when installing network operator, setting up RDMA networking, deploying SR-IOV, running ins-network-operator.sh, generating Helm values, applying network CRDs, or troubleshooting deployment failures.
Manage SR-IOV virtual functions, PCI devices, link speed, and RDMA testing for NVIDIA Network Operator. Use when setting VFs, querying PCI devices, forcing link speed, running RDMA bandwidth tests, checking RDMA capability, managing node labels and taints, or cordoning nodes.
Run and create tests for netop-tools configuration generation. Use when running unitest.sh, validating YAML generation, creating new test cases, checking test baselines, debugging test failures, or verifying config changes don't break existing tests.
Diagnose and fix NVIDIA Network Operator issues in Kubernetes. Use when pods can't get RDMA network, SR-IOV VFs not showing, IP allocation failures, network attachment missing, must-gather diagnostics, operator pods crashing, NicClusterPolicy errors, or IPAM pool exhaustion.
| name | upgrading-network-operator |
| description | Upgrade NVIDIA Network Operator to a new version. Use when changing NETOP_VERSION, running upgrade-network-operator.sh, migrating between operator versions, handling CRD schema changes, or rolling back a failed upgrade. |
Upgrade the Network Operator Helm release to a new version with zero-downtime node rolling.
24.7.0, 24.10.0, 24.10.1, 25.1.0, 25.4.0, 25.7.0, 25.10.0, 26.1.0 (default)
helm search repo nvidia/network-operator --versionsCREATE_CONFIG_ONLY=1 firstkubectl get nodes# 1. Set new version
export NETOP_VERSION="26.1.0"
source global_ops.cfg
# 2. Preview config changes (dry run)
export CREATE_CONFIG_ONLY=1
cd usecase/${USECASE}
${NETOP_ROOT_DIR}/ops/mk-config.sh
# Review generated YAML
# 3. Run upgrade
export CREATE_CONFIG_ONLY=0
${NETOP_ROOT_DIR}/upgrade/upgrade-network-operator.sh
mk-values.sh, mk-nic-cluster-policy.sh, mk-network-cr.shapplycrds.shapply-network-cr.shNIC_CONFIG_ENABLE=true)helm upgradekubectl get pods -n ${NETOP_NAMESPACE}
./ops/getnetwork.sh
./ops/checksriovstate.sh
./ops/syncsriov.sh
./ops/checkipam.sh
| Version | Key Changes |
|---|---|
| 25.10.* | MAINTENANCE_OPERATOR_ENABLE defaults to NIC_CONFIG_ENABLE value |
| 26.1.* | MAINTENANCE_OPERATOR_ENABLE defaults to true independently |
| 25.1.0 | Uses nicConfigurationOperator parameter (older API) |
| 25.4.0+ | Uses deployNodeFeatureRules for NFD |
If upgrade fails, restore previous config and re-run:
export NETOP_VERSION="<previous_version>"
source global_ops.cfg
${NETOP_ROOT_DIR}/upgrade/upgrade-network-operator.sh
| Symptom | Fix |
|---|---|
| Helm chart not found | Verify NETOP_VERSION and helm repo update |
| CRD validation errors | Check feature gate compatibility with new version |
| Nodes stuck cordoned | Run source ops/cordon.sh && uncordon |
| Finalizers blocking delete | ./ops/getfinalizers.sh, then patch to remove |