Skip to content

Commit 54a3c54

Browse files
ybettank8s-ci-robot
authored andcommitted
Documenting the new initContainer new option in the DevicePlugin.
Signed-off-by: Yoni Bettan <[email protected]>
1 parent 97da858 commit 54a3c54

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

docs/mkdocs/documentation/deploy_kmod.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,13 @@ That DaemonSet will target nodes:
3535
- that match the `Module`'s `.spec.selector`;
3636
- on which the kernel module is loaded.
3737

38+
There is also support for running an init-container as part of the device-plugin by setting `.spec.devicePlugin.initContainer`.
39+
40+
For example, for some devices, a successful load of the kernel module into the kernel might not constitute the indication of
41+
successful loading. For those devices, the indication is the appearance of the device file under /dev filesystem.
42+
For those cases, using an init-container looping over files verification instead of adding that verification to the device-plugin
43+
image is preferable for debuggability and code re-usage reasons.
44+
3845
## `Module` CRD
3946

4047
The `Module` Custom Resource Definition represents a kernel module that should be loaded on all or select nodes in the

0 commit comments

Comments
 (0)