Skip to content

Commit 844d479

Browse files
StephenJamesSmithopenshift-cherrypick-robot
authored andcommitted
TELCODOCS-2311: Using in-tree modules
1 parent dd1740c commit 844d479

File tree

2 files changed

+28
-0
lines changed

2 files changed

+28
-0
lines changed

hardware_enablement/kmm-kernel-module-management.adoc

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,9 @@ include::modules/kmm-example-module-cr.adoc[leveloffset=+2]
5959
.Additional resources
6060
* xref:../security/certificates/updating-ca-bundle.adoc#ca-bundle-replacing_updating-ca-bundle[Replacing the CA Bundle certificate]
6161
62+
// Added for TELCODOCS-2311
63+
include::modules/kmm-using-intree-modules.adoc[leveloffset=+1]
64+
6265
// Added for TELCODOCS-1827
6366
include::modules/kmm-symbolic-links-for-in-tree-dependencies.adoc[leveloffset=+1]
6467

modules/kmm-using-intree-modules.adoc

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * hardware_enablement/kmm-kernel-module-management.adoc
4+
5+
:_mod-docs-content-type: CONCEPT
6+
[id="kmm-using-intree-modules_{context}"]
7+
8+
= Using in-tree modules with the device plugin
9+
10+
In some cases, you might need to configure the KMM Module to avoid loading an out-of-tree kernel module and instead use the in-tree module, running only the device plugin. In such cases, you can omit the `moduleLoader` parameter from the `Module` custom resource (CR), and leave only the `devicePlugin` section, as shown in the following example.
11+
12+
.Example `Module` CR
13+
[source,yaml]
14+
----
15+
apiVersion: kmm.sigs.x-k8s.io/v1beta1
16+
kind: Module
17+
metadata:
18+
name: my-kmod
19+
spec:
20+
selector:
21+
node-role.kubernetes.io/worker: ""
22+
devicePlugin:
23+
container:
24+
image: some.registry/org/my-device-plugin:latest
25+
----

0 commit comments

Comments
 (0)