deploy: d4facd7

release-notes.html

@@ -383,51 +383,45 @@ <h2>Known Limitations<a class="headerlink" href="#known-limitations" title="Perm
 </tr>
 </thead>
 <tbody>
-<tr class="row-even"><td><p>All</p></td>
-<td><div class="line-block">
-<div class="line">- MOFED container builds and loads the driver on every MOFED Pod startup to support the current OS kernel.</div>
-</div>
-</td>
-</tr>
-<tr class="row-odd"><td><p>23.10.0</p></td>
+<tr class="row-even"><td><p>23.10.0</p></td>
 <td><div class="line-block">
 <div class="line">- IPoIB sub-interface creation does not work on RHEL 8.8 and RHEL 9.2 due to the kernel limitations in these distributions. This means that IPoIBNetwork cannot be used with these operating systems.</div>
 </div>
 </td>
 </tr>
-<tr class="row-even"><td><p>23.4.0</p></td>
+<tr class="row-odd"><td><p>23.4.0</p></td>
 <td><div class="line-block">
 <div class="line">- 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.</div>
 </div>
 </td>
 </tr>
-<tr class="row-odd"><td><p>23.1.0</p></td>
+<tr class="row-even"><td><p>23.1.0</p></td>
 <td><div class="line-block">
 <div class="line">- Only a single PKey can be configured per IPoIB workload pod.</div>
 </div>
 </td>
 </tr>
-<tr class="row-even"><td><p>1.4.0</p></td>
+<tr class="row-odd"><td><p>1.4.0</p></td>
 <td><div class="line-block">
 <div class="line">- 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.</div>
 <div class="line">- 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.</div>
 </div>
 </td>
 </tr>
-<tr class="row-odd"><td><p>1.3.0</p></td>
+<tr class="row-even"><td><p>1.3.0</p></td>
 <td><div class="line-block">
 <div class="line">- MOFED container is not a supported configuration on the DGX platform.</div>
 <div class="line">- 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.</div>
 </div>
 </td>
 </tr>
-<tr class="row-even"><td><p>1.2.0</p></td>
+<tr class="row-odd"><td><p>1.2.0</p></td>
 <td><div class="line-block">
 <div class="line">- N/A</div>
 </div>
 </td>
 </tr>
-<tr class="row-odd"><td><p>1.1.0</p></td>
+<tr class="row-even"><td><p>1.1.0</p></td>
 <td><div class="line-block">
 <div class="line">- NicClusterPolicy update is not supported at the moment.</div>
 <div class="line">- Network Operator is compatible only with NVIDIA GPU Operator v1.9.0 and above.</div>
@@ -437,7 +431,7 @@ <h2>Known Limitations<a class="headerlink" href="#known-limitations" title="Perm
 </div>
 </td>
 </tr>
-<tr class="row-even"><td><p>1.0.0</p></td>
+<tr class="row-odd"><td><p>1.0.0</p></td>
 <td><div class="line-block">
 <div class="line">- Network Operator is only compatible with NVIDIA GPU Operator v1.5.2 and above.</div>
 <div class="line">- Persistent NICs configuration for netplan or ifupdown scripts is required for SR-IOV and Shared RDMA interfaces on the host.</div>