github NVIDIA/k8s-device-plugin v0.7.0-rc.1

latest releases: v0.15.0, v0.15.0-rc.2, v0.14.5...
pre-release3 years ago
  • 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:

  1. 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 an nvidia.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 or nvidia.com/mig-3g.20gb: 2) without problems.
  2. 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.

Don't miss a new k8s-device-plugin release

NewReleases is sending notifications on new releases.