Release Notes

- Added support for OpenShift Container Platform v4.16.
- Added support for NVIDIA Grace based ARM platforms with OpenShift Container Platform.
- Added support for RHEL v8.9, v8.10, v9.3 and v9.4 with Upstream K8s and Containerd runtime.
- Added support for Switchdev mode SR-IOV mode with OVS CNI with RHEL.

- Added support for OpenShift Container Platform v4.15.
- Added support for Ubuntu 24.04.
- Added support for NVIDIA Grace based ARM platforms with Ubuntu 22.04 and Upstream K8s as a Tech Preview feature.
- Added support for NVIDIA IGX Orin based ARM platforms with Ubuntu 22.04 and Upstream K8s as a GA feature.
- Added support for Precompiled DOCA Driver containers for Ubuntu 22.04.
- Added support for Switchdev SR-IOV mode with SR-IOV Network Operator and OVS CNI as a Tech Preview feature.
- Added support for DOCA Telemetry Service (DTS) integration to expose network telemetry and NIC metrics in K8s.
- Added support for network namespace isolation of RDMA devices with RDMA CNI
- Added support for RHEL and OpenShift deployments with Real-time kernels.
- Enhanced DOCA Driver container deployment and significantly reduced compilation time after node reboots.

- Added support for OpenShift Container Platform v4.14.
- Added support for RHEL v8.8.
- Optimized SR-IOV NIC configuration time with Network Operator (vanilla Kubernetes only).
- Added a validating admission controller for NVIDIA Network Operator.
- Added support for NIC Feature Discovery (driver version discovery).
- Added CDI support for SR-IOV Network Device Plugin and RDMA Shared Device Plugin for network device persistency.
- Added support for NVIDIA BlueField-3 NIC mode.
- Added High-Availability and Leader election support for NV-IPAM.
- Added systemd mode support for SR-IOV Network Operator and MOFED container to optimize cluster/node startup time.

- Added support for NVIDIA IPAM Plugin deployment.
- Added support for CRDs upgrade during NVIDIA Network Operator installation or upgrade.

- 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.

- Added support for Kubernetes >= 1.17 and <=1.24.
- Added the option to use a single namespace to deploy Network Operator components.
- Added support for automatic MLNX OFED driver upgrade.
- Added support for IPoIB CNI.
- Added support for Air Gap deployment.

- Added support for OpenShift Container Platform 4.9.
- Added support for Network Operator upgrade from v1.0.0.
- Added support for Kubernetes POD Security Policy.
- Added support for Kubernetes >= 1.17 and <=1.22.
- Added the ability to propagate nodeAffinity property from the NicClusterPolicy to Network Operator dependencies.

- Deploying NicClusterPolicy Custom Resource through helm is deprecated, support will be removed in Network Operator 24.10. It is advised to keep deployCR=false in your helm values and create/update NicClusterPolicy Custom Resource post helm install/update.

- Dropped MLNX_OFED support for versions older than 5.7-0.1.2.0.
- Removed nv-peer-mem support in favor of nvidia-peer-mem.

- 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”.

- Fixed a cluster scale-up issue.
- Fixed an issue with IPoIB CNI deployment in OCP.

- N/A

• In case ENABLE_NFSRDMA is enabled for DOCA Driver container and NVMe modules are loaded in the host system, NVIDA DOCA Driver Container will fail to load. User should blacklist NVMe modules to prevent them from loading on system boot. if this is not possible (e.g when the system uses NVMe SSD drives) then ENABLE_NFSRDMA must be set to false. Using features such as GPU Direct Storage is not supported in such case.

- In case that the UNLOAD_STORAGE_MODULES parameter is enabled for MOFED container deployment, it is required to make sure that the relevant storage modules are not in use in the OS.

- The operator upgrade procedure does not reflect configuration changes. The RDMA Shared Device Plugin or SR-IOV Device Plugin should be restarted manually in case of configuration changes.
- The RDMA subsystem could be exclusive or shared only in one cluster. Mixed configuration is not supported. The RDMA Shared Device Plugin requires shared RDMA subsystem.

- N/A

- 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.