-
Notifications
You must be signed in to change notification settings - Fork 212
gpu: copy nfdhook functionality to gpu-plugin #1492
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gpu: copy nfdhook functionality to gpu-plugin #1492
Conversation
bbc8d79 to
218a29d
Compare
Codecov Report
@@ Coverage Diff @@
## main #1492 +/- ##
==========================================
- Coverage 50.04% 49.52% -0.52%
==========================================
Files 43 42 -1
Lines 4884 4917 +33
==========================================
- Hits 2444 2435 -9
- Misses 2301 2341 +40
- Partials 139 141 +2
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
deployments/gpu_plugin/overlays/initcontainer/use-initcontainer.yaml
Outdated
Show resolved
Hide resolved
c8a62e9 to
107d8a0
Compare
|
My main issues have been fixed (last two items are more of nit-picking), so I think it would be time for other(s) review this too. @uniemimu ? |
107d8a0 to
302a14b
Compare
302a14b to
fc959f6
Compare
fc959f6 to
1511b06
Compare
|
Changes in the PR:
|
1511b06 to
5532976
Compare
LGTM.
Update the README table to match this change? |
Yes, that's needed. It might make sense to add the labeling info to GPU plugin also. Or create a new .md to which both initcontainer and plugin points to. |
eero-t
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed other than the operator code (as I'm not familiar enough with that).
deployments/nfd/overlays/node-feature-rules/platform-labeling-rules.yaml
Outdated
Show resolved
Hide resolved
deployments/nfd/overlays/node-feature-rules/platform-labeling-rules.yaml
Outdated
Show resolved
Hide resolved
deployments/nfd/overlays/node-feature-rules/platform-labeling-rules.yaml
Outdated
Show resolved
Hide resolved
deployments/nfd/overlays/node-feature-rules/platform-labeling-rules.yaml
Outdated
Show resolved
Hide resolved
d43b1f4 to
b8dc72a
Compare
|
PTAL I'll squash the commits once approved. |
|
LGTM |
|
FYI: we've had some internal discussion on how to best label things, so label rules & names have been changing a bit, but we should have now consensus on final ones (i.e. there will be one more small update to them with squash). |
55e57e3 to
4235e69
Compare
|
@hj-johannes-lee can you please review? |
|
@uniemimu this should be OK to merge I think |
4235e69 to
01d5042
Compare
NFD v0.14+ doesn't support binary NFD hooks by default, so there is a need to move the label creation away from the GPU nfdhook. Move extended resource label creation to plugin, and drop labels that were already marked deprecated (platform_gen, media_version etc.). Drop init-container from deployment files and operator. It is still possible to use an initcontainer, but the default deployments do not support it. Signed-off-by: Tuomas Katila <[email protected]>
Signed-off-by: Tuomas Katila <[email protected]>
Signed-off-by: Tuomas Katila <[email protected]>
01d5042 to
bd2a35d
Compare
In order to support v0.14+ NFD and extended resources, write node labels into a file and store it for NFD's features.d directory.
The old functionality still exists in the initcontainer, but if it's used NFD has to be configured to allow it.
Fixes #1181