feat: add nvidia shared GPU settings to k8s model #49
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
This PR introduces two new fields within the
NvidiaDevicePluginSettings
structure:max_sharing_per_gpu
andrename_shared_gpu
. These new fields are for managing the timeslicing capabilities of Nvidia GPUs.Setting
max_sharing_per_gpu
to 1 deactivates time-slicing, effectively disabling GPU sharing. Conversely, a value greater than 1 activates time-slicing, resulting in the creation of the specified number of GPU replicas.The
rename_shared_gpu
field dictates the naming convention for shared GPU resources. Afalse
value retains the original GPU name, whiletrue
triggers a renaming process, appending.shared
to the GPU identifier. For instance, enabling this feature would transformnvidia.com/gpu
tonvidia.com/gpu.shared
.By contributing this pull request, I grant permission to use, modify, replicate, and distribute my submission, in accordance with your preferred terms.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice."