Fix docs usability and known issues#355
Merged
a-mccarthy merged 5 commits intoNVIDIA:mainfrom Mar 4, 2026
Merged
Conversation
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Documentation preview |
cdesiniotis
reviewed
Mar 2, 2026
gpu-operator/release-notes.rst
Outdated
Comment on lines
+89
to
+92
| * When using RKE2 on RHEL 9.6 with SELinux enforcing mode enabled, the MIG Manager will not install correctly. | ||
| This happens because the GPU Operator doesn't have the correct permissions to read from the feature file directly on nodes in the cluster. | ||
| This prevents the GPU Operator from correctly evaluating if a node has MIG-capable GPUs on it and whether the GPU Operator should deploy the MIG Manager. | ||
| Workaround this issue by enabling NVIDIA GPU Feature Discovery to use the Node Feature API by default in ClusterPolicy: |
Contributor
There was a problem hiding this comment.
Suggested change
| * When using RKE2 on RHEL 9.6 with SELinux enforcing mode enabled, the MIG Manager will not install correctly. | |
| This happens because the GPU Operator doesn't have the correct permissions to read from the feature file directly on nodes in the cluster. | |
| This prevents the GPU Operator from correctly evaluating if a node has MIG-capable GPUs on it and whether the GPU Operator should deploy the MIG Manager. | |
| Workaround this issue by enabling NVIDIA GPU Feature Discovery to use the Node Feature API by default in ClusterPolicy: | |
| * When deploying the GPU Operator on systems with SELinux in enforcing mode, the MIG Manager will not get scheduled to GPU nodes. This is because the GPU Feature Discovery pod, which adds a label to nodes indicating if a MIG-capable GPU is present, fails to label nodes due to insufficient permissions on Node Feature Discovery's feature file drop-in directory. Workaround this issue by configuring NVIDIA GPU Feature Discovery to use the Node Feature API instead of feature files in ClusterPolicy: |
Contributor
There was a problem hiding this comment.
Here is my suggestion for how to word this. Feel free to push back.
Collaborator
Author
There was a problem hiding this comment.
@cdesiniotis thanks! i made some updates here, can you take another look?
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
a-mccarthy
changed the title
cdesiniotis
approved these changes
Mar 3, 2026
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
Signed-off-by: Abigail McCarthy <20771501+a-mccarthy@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR includes