jahanson/theshire
1
0
Fork 0
Code Issues 1 Pull requests 9 Projects Releases Packages Wiki Activity Actions

Update Helm release nvidia-device-plugin to v0.16.0 #382

Merged
jahanson merged 1 commit from renovate/nvidia-device-plugin-0.x into main 2024-07-17 11:31:49 -05:00
Conversation 0 Commits 1 Files changed 1 +1 -1
smeagol-help commented 2024-06-25 07:35:40 -05:00
Collaborator
Copy link

This PR contains the following updates:

Package Update Change
nvidia-device-plugin minor 0.14.5 -> 0.16.0

Release Notes

NVIDIA/k8s-device-plugin (nvidia-device-plugin)

v0.16.0

Compare Source

  • Fixed logic of atomic writing of the feature file
  • Replaced WithDialer with WithContextDialer
  • Fixed SELinux context of MPS pipe directory.
  • Changed behavior for empty MIG devices to issue a warning instead of an error when the mixed strategy is selected
  • Added a a GFD node label for the GPU mode.
  • Update CUDA base image version to 12.5.1

v0.15.1

Compare Source

Changelog

  • Fix inconsistent usage of hasConfigMap helm template. This addresses cases where certain resources (roles and service accounts) would be created even if they were not required.
  • Raise an error in GFD when MPS is used with MIG. This ensures that the behavior across GFD and the Device Plugin is consistent.
  • Remove provenance information from published images.
  • Use half of total memory for size of MPS tmpfs by default.

v0.15.0

Compare Source

  • Moved nvidia-device-plugin.yml static deployment at the root of the repository to deployments/static/nvidia-device-plugin.yml.
  • Simplify PCI device clases in NFD worker configuration.
  • Update CUDA base image version to 12.4.1.
  • Switch to Ubuntu22.04-based CUDA image for default image.
  • Add new CUDA driver and runtime version labels to align with other NFD version labels.
  • Update NFD dependency to v0.15.3.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [nvidia-device-plugin](https://github.com/NVIDIA/k8s-device-plugin) | minor | `0.14.5` -> `0.16.0` | --- ### Release Notes <details> <summary>NVIDIA/k8s-device-plugin (nvidia-device-plugin)</summary> ### [`v0.16.0`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0160) [Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.15.1...v0.16.0) - Fixed logic of atomic writing of the feature file - Replaced `WithDialer` with `WithContextDialer` - Fixed SELinux context of MPS pipe directory. - Changed behavior for empty MIG devices to issue a warning instead of an error when the mixed strategy is selected - Added a a GFD node label for the GPU mode. - Update CUDA base image version to 12.5.1 ### [`v0.15.1`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.15.1) [Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.15.0...v0.15.1) #### Changelog - Fix inconsistent usage of `hasConfigMap` helm template. This addresses cases where certain resources (roles and service accounts) would be created even if they were not required. - Raise an error in GFD when MPS is used with MIG. This ensures that the behavior across GFD and the Device Plugin is consistent. - Remove provenance information from published images. - Use half of total memory for size of MPS tmpfs by default. ### [`v0.15.0`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#Version-v0150) [Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.14.5...v0.15.0) - Moved `nvidia-device-plugin.yml` static deployment at the root of the repository to `deployments/static/nvidia-device-plugin.yml`. - Simplify PCI device clases in NFD worker configuration. - Update CUDA base image version to 12.4.1. - Switch to Ubuntu22.04-based CUDA image for default image. - Add new CUDA driver and runtime version labels to align with other NFD version labels. - Update NFD dependency to v0.15.3. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTUuMCIsInVwZGF0ZWRJblZlciI6IjM3LjQzMS43IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
smeagol-help force-pushed renovate/nvidia-device-plugin-0.x from 7738b66d45 to b31f1b3357 2024-07-16 09:02:19 -05:00 Compare
smeagol-help changed title from Update Helm release nvidia-device-plugin to v0.15.1 to Update Helm release nvidia-device-plugin to v0.16.0 2024-07-16 09:02:20 -05:00
jahanson merged commit 6cf46ec432 into main 2024-07-17 11:31:49 -05:00
jahanson deleted branch renovate/nvidia-device-plugin-0.x 2024-07-17 11:31:50 -05:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: jahanson/theshire#382
No description provided.
Delete branch "renovate/nvidia-device-plugin-0.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?