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
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.
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. If one desires to use it then, NFD's default configuration has to be modified to allow binary hooks. Due to the change, GPU binary hook's functionality has been copied to GPU plugin.
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
| -shared-dev-num | int | 1 | Number of containers that can share the same GPU device |
54
54
| -allocation-policy | string | none | 3 possible values: balanced, packed, none. For shared-dev-num > 1: _balanced_ mode spreads workloads among GPU devices, _packed_ mode fills one GPU fully before moving to next, and _none_ selects first available device from kubelet. Default is _none_. Allocation policy does not have an effect when resource manager is enabled. |
0 commit comments