Skip to content

Commit

Permalink
Merge pull request #145 from e0ne/remove-outdated-upgrade-notice
Browse files Browse the repository at this point in the history
fix: Remove outdated upgrade instructions
  • Loading branch information
e0ne authored Nov 25, 2024
2 parents e332fd6 + 5254d9d commit eef7319
Showing 1 changed file with 0 additions and 31 deletions.
31 changes: 0 additions & 31 deletions docs/getting-started-kubernetes.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1313,37 +1313,6 @@ To apply SR-IOV configuration on several nodes in parallel, create a ``SriovNetw
- key: other-label
operator: "Exists"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Upgrade from NVIDIA Network Operator v24.1.0
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

To upgrade SR-IOV Network operator you need to create ``SriovNetworkPoolConfig`` CR with the number of nodes to be configured in a parallel as we did in `SriovOperatorConfig`` in previous releases.

E.g.: old method to configure nodes in a parallel:

.. code-block:: bash
kubectl patch sriovoperatorconfigs.sriovnetwork.openshift.io -n nvidia-network-operator default --patch '{ "spec": { "maxParallelNodeConfiguration": 5 } }' --type='merge'
New method to configure nodes in a parallel:

``sriov-network-pool-config-new.yaml``

.. code-block:: yaml
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkPoolConfig
metadata:
name: pool-1
namespace: nvidia-network-operator
spec:
maxUnavailable: "5"
nodeSelector:
- matchExpressions:
- key: node-role.kubernetes.io/master
operator: Exists
--------------------------------------------------------------------------
SR-IOV Network Operator Deployment – Parallel NIC Configuration for SR-IOV
--------------------------------------------------------------------------
Expand Down

0 comments on commit eef7319

Please sign in to comment.