Skip to content

Commit 3f65e67

Browse files
committed
docs(gpu): fix the example resourceName in the upgrade note
The upgrade step had the slug example backwards — it presented the tidy nvidia.com/TU104GL_T4 as what the sandbox device plugin emits and TU104GL_TESLA_T4 as a legacy name. It is the other way around: the plugin upper-cases the PCI-IDs name and keeps the Tesla brand, so a vanilla plugin advertises nvidia.com/TU104GL_TESLA_T4. Point operators at the slug the plugin actually generates and note it can vary by plugin build. Assisted-By: Claude <[email protected]> Signed-off-by: Aleksei Sviridkin <[email protected]>
1 parent 1b11871 commit 3f65e67

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • content/en/docs/next/virtualization

‎content/en/docs/next/virtualization/gpu.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,7 +159,7 @@ Before upgrading:
159159
160160
2. Move any custom entries into the Platform Package values under `.gpu.permittedHostDevices` (set `.gpu.replaceDefaults: true` if you want only your own list instead of appending to the NVIDIA defaults).
161161
162-
3. Verify every `resourceName` against what your nodes actually advertise — the default table uses `nvidia-sandbox-device-plugin` slugs (e.g. `nvidia.com/TU104GL_T4`) that differ from legacy driver names (e.g. `TU104GL_TESLA_T4`):
162+
3. Verify every `resourceName` against what your nodes actually advertise. The default table carries the slug `nvidia-sandbox-device-plugin` generates from each card's PCI-IDs name (uppercased, e.g. `nvidia.com/TU104GL_TESLA_T4` for a Tesla T4), but a different plugin build or PCI-IDs snapshot can emit a different string:
163163

164164
```bash
165165
kubectl describe node <node> | grep nvidia.com/

0 commit comments

Comments
 (0)