feat: GPU Op 26.7.1 - #512
Conversation
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
Documentation preview |
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
| - NVIDIA Confidential Computing Manager for Kubernetes v0.4.4 | ||
|
|
||
| * Added support for NVIDIA Data Center GPU Driver 615.71.09. | ||
|
|
There was a problem hiding this comment.
List of issues fixed:
GPU Operator
NVIDIA/gpu-operator#2914
NVIDIA/gpu-operator#2874
NVIDIA/gpu-operator#2776
NVIDIA/gpu-operator#2237
Device Plugin / GFD
NVIDIA/k8s-device-plugin#1891
MIG Manager
NVIDIA/mig-parted#485
Container Toolkit
NVIDIA/nvidia-container-toolkit#2026
NVIDIA/nvidia-container-toolkit#1477
NVIDIA/nvidia-container-toolkit#563
NVIDIA/nvidia-container-toolkit#1982
NVIDIA/nvidia-container-toolkit#648
Driver Manager / VFIO
NVIDIA/k8s-driver-manager#190
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
| Fixed Issues | ||
| ------------ | ||
|
|
||
| * Fixed an issue where GPU Feature Discovery could not update a ``NodeFeature`` resource because its role did not permit deleting ``NodeFeature`` resources. |
There was a problem hiding this comment.
It's worth clarifying that this error is only reproducible when the OwnerReferencesPermissionEnforcement admission controller is enabled in Kubernetes cluster.
There was a problem hiding this comment.
Before this fix, GFD would fail when OwnerReferencesPermissionEnforcement was enabled. After this fix, this failure will no longer occur.
Signed-off-by: Mike McKiernan <mmckiernan@nvidia.com>
3 participants
RNs: https://nvidia.github.io/cloud-native-docs/review/pr-512/gpu-operator/latest/release-notes.html#v26-7-1
matrix: https://nvidia.github.io/cloud-native-docs/review/pr-512/gpu-operator/latest/platform-support.html#gpu-operator-component-matrix