Added support for NicClusterPolicy update and removal.

Added support for OpenShift Container Platform 4.11 and 4.12.

• Added a calendar versioning schema for Network Operator releases to better align with the NVIDIA GPU Operator.

• Added support for the following operating systems and Kubernetes environments:
• RHEL 8.4 and 8.6 with CRI-O container runtime
• Kubernetes >= 1.21 and <=1.26

• Added PKey configuration for IB networks with IB-Kubernetes.

• Added the ability to gracefully terminate the OFED container on DGX systems running Red Hat OpenShift.

• Macvlan Network
• HostDevice Network
• SR-IOV Network

• Network Operator 1.2.0 deploys the NVIDIA MLNX_OFED 5.6 driver container by default. When deployed, depending on your system kernel and OS configuration, the network device name may change, as it no longer installs an udev rule to force network device naming scheme. Instead, the default setting uses the name already configured in the system by either systemd.network or any pre-existing udev rules (e.g enp3s0f0 netdev will change to enp3s0f0np0). If that is the case in your system, please make sure to update the following:
  • The master network device name in your MacvlanNetwork 

  • The ifNames selector, if used in RDMA shared device plugin resource configuration

  • The pfNames selector, if used in SR-IOV device plugin configuration

  • If the sriov-network-operator is used, any instance of SriovNetworkNodePolicy which utilizes NicSelector.PfNames field should be updated to the new network device name. 
• When Network Operator 1.2.0 is installed via Helm, it no longer deploys both RDMA shared device plugin and SR-IOV network device plugin by default, as it may cause the same device to be registered to two different device plugins. This is an undesirable behavior. Instead, by default, only RDMA shared device plugin is deployed via Helm.
  If you wish to deploy both device plugins, set the `sriovDevicePlugin.deploy` Helm parameter to "true".

Node Feature Discovery

v0.10.1

Optionally deployed. May already be present in the cluster with proper configuration.

NVIDIA MLNX_OFED driver container 

5.8-1.0.1.1.2

-

nv-peer-mem driver container

1.1-0

-

k8s-rdma-shared-device-plugin

v1.3.2

-

sriov-network-device-plugin

v3.5.1

-

containernetworking CNI

v0.8.7

-

whereabouts CNI

V0.5.2

-

multus CNI

v3.8

-

MOFED container is not a supported configuration on the DGX platform.

MOFED container deletion may lead to the driver's unloading: In this case, the mlx5_core kernel driver must be reloaded manually. Network connectivity could be affected if there are only NVIDIA NICs on the node.

NicClusterPolicy update is not supported at the moment. 

Network Operator is compatible only with NVIDIA GPU Operator v1.9.0 and above. 

GPUDirect could have performance degradation if it is used with servers which are not optimized. Please see official GPUDirect documentation here. 

Persistent NICs configuration for netplan or ifupdown scripts is required for SR-IOV and Shared RDMA interfaces on the host.

POD Security Policy admission controller should be enabled to use PSP with Network Operator. Please see Deployment with Pod Security Policy in the Network Operator Documentation for details.

Network Operator is only compatible with NVIDIA GPU Operator v1.5.2 and above.

Persistent NICs configuration for netplan or ifupdown scripts is required for SR-IOV and Shared RDMA interfaces on the host.