You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cmd/gpu_plugin/README.md
+14Lines changed: 14 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ Table of Contents
16
16
*[Running GPU plugin as non-root](#running-gpu-plugin-as-non-root)
17
17
*[Labels created by GPU plugin](#labels-created-by-gpu-plugin)
18
18
*[SR-IOV use with the plugin](#sr-iov-use-with-the-plugin)
19
+
*[CDI support](#cdi-support)
19
20
*[KMD and UMD](#kmd-and-umd)
20
21
*[Issues with media workloads on multi-GPU setups](#issues-with-media-workloads-on-multi-gpu-setups)
21
22
*[Workaround for QSV and VA-API](#workaround-for-qsv-and-va-api)
@@ -218,6 +219,19 @@ GPU plugin does __not__ setup SR-IOV. It has to be configured by the cluster adm
218
219
219
220
GPU plugin does however support provisioning Virtual Functions (VFs) to containers for a SR-IOV enabled GPU. When the plugin detects a GPU with SR-IOV VFs configured, it will only provision the VFs and leaves the PF device on the host.
220
221
222
+
### CDI support
223
+
224
+
GPU plugin supports [CDI](https://github.com/container-orchestrated-devices/container-device-interface) to provide device details to the container. It does not yet provide any benefits compared to the traditional Kubernetes Device Plugin API. The CDI device specs will improve in the future with features that are not possible with the Device Plugin API.
225
+
226
+
To enable CDI support, container runtime has to support it. The support varies depending on the versions:
227
+
* CRI-O supports CDI by default v1.24.0 onwards.
228
+
* Containerd supports CDI from 1.7.0 onwards. 2.0.0 release will enable it by default.
229
+
* Docker supports CDI from v25 onwards.
230
+
231
+
Kubernetes CDI support is included since 1.28 release. In 1.28 it needs to be enabled via `DevicePluginCDIDevices` feature gate. From 1.29 onwards the feature is enabled by default.
232
+
233
+
> *NOTE*: To use CDI outside of Kubernetes, for example with Docker or Podman, CDI specs can be generated with the [Intel CDI specs generator](https://github.com/intel/intel-resource-drivers-for-kubernetes/releases/tag/specs-generator-v0.1.0).
234
+
221
235
### KMD and UMD
222
236
223
237
There are 3 different Kernel Mode Drivers (KMD) available: `i915 upstream`, `i915 backport` and `xe`:
0 commit comments