remove dependency on /etc/os-release host mount#2138
Merged
Conversation
tariq1890
requested review from
cdesiniotis,
karthikvetrivel,
rahulait,
rajathagasthya and
shivamerla
as code owners
tariq1890
force-pushed
the
rm-os-release
branch
2 times, most recently
from
580d036 to
36717e5
Compare
rahulait
reviewed
Feb 19, 2026
Signed-off-by: Tariq Ibrahim <tibrahim@nvidia.com>
tariq1890
force-pushed
the
rm-os-release
branch
from
36717e5 to
14a6a02
Compare
cdesiniotis
approved these changes
Feb 19, 2026
rajathagasthya
approved these changes
Feb 19, 2026
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
5 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 builds on top of #2101 - using the NFD labels to get the
/etc/os-releaseinformation instead of directly querying the node's/etc/os-releasefile via a host mount.With the existing approach, the gpu-operator assumes that the node on which the gpu-operator pod is scheduled has the same OS as the GPU node. There are cases where users may choose to deploy the gpu-operator pod on a CPU node having an OS different from that of the GPU node. These changes enable the gpu-operator to function in these scenarios.