You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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]>
Copy file name to clipboardExpand all lines: cmd/gpu_nfdhook/README.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,6 +11,8 @@ Table of Contents
11
11
12
12
## Introduction
13
13
14
+
***NOTE:*** NFD's binary hook support will be turned off by default in the 0.14 release. The functionality in the GPU NFD hook is moved into a new NFD rule and into GPU plugin, and the capability labels are being removed completely. The GPU plugin deployment doesn't anymore support using init container. This directory will be removed in the future.
15
+
14
16
This is the [Node Feature Discovery](https://github.com/kubernetes-sigs/node-feature-discovery)
15
17
binary hook implementation for the Intel GPUs. The intel-gpu-initcontainer (which
16
18
is built with the other images) can be used as part of the gpu-plugin deployment
0 commit comments