Releases: NVIDIA/k8s-device-plugin
Releases · NVIDIA/k8s-device-plugin
v0.7.0-rc.1
- Added
migStrategy
as a parameter to select the MIG strategy to the helm chart - Add support for MIG with different strategies {none, single, mixed}
- Update vendored NVML bindings to latest (to include MIG APIs)
- Add license in UBI image
- Update UBI image with certification requirements
MIG support in this release has some known limitations when running under the mixed
strategy:
- Only one device type can be requested by a container at a time. If more than one device type is requested, it is undefined which one the container will actually get access to. For example, a container cannot request both an
nvidia.com/gpu
and annvidia.com/mig-3g.20gb
at the same time. However, it can request multiple instances of the same resource type (e.g.nvidia.com/gpu: 2
ornvidia.com/mig-3g.20gb: 2
) without problems. - If you do happen to request multiple resource types, kubernetes will still allocate / bill all of the resources to your container. You just wont be able to see / access any of them except one.
In practice, this shouldn't be a problem because CUDA wouldn't be able to leverage more than one of these resource types at a time anyway. That said, we plan to fix this problem by the time the full v0.7.0
release of this plugin becomes available. So stay tuned.
v0.6.0
v0.5.0
- Add a new plugin.yml variant that is compatible with the CPUManager
- Change CMD in Dockerfile to ENTRYPOINT
- Add flag to optionally return list of device nodes in Allocate() call
- Refactor device plugin to eventually handle multiple resource types
- Move plugin error retry to event loop so we can exit with a signal
- Update all vendored dependencies to their latest versions
- Fix bug that was inadvertently always disabling health checks
- Update minimal driver version to 384.81
v0.4.0
v0.3.0
- Manifest is updated for Kubernetes 1.16+ (apps/v1)
- Adds more logging information