openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

MGMT-16631: Dev/QE review

Browse Source
This commit is contained in:
StephenJamesSmith
2024-05-30 09:34:14 -04:00
committed by openshift-cherrypick-robot
parent ed98271001
commit 22edfafe93
2 changed files with 10 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
hardware_enablement/kmm-kernel-module-management.adoc
View File

@@ -51,10 +51,13 @@ include::modules/kmm-replacing-in-tree-modules-with-out-of-tree-modules.adoc[lev
[role="_additional-resources"]
.Additional resources
* link:https://fastbitlab.com/building-a-linux-kernel-module/[Building a linux kernel module]
include::modules/kmm-example-module-cr.adoc[leveloffset=+2]
// Added for MGMT-16631
[role="_additional-resources"]
.Additional resources
* xref:../security/certificates/updating-ca-bundle.adoc#ca-bundle-replacing_updating-ca-bundle[Replacing the CA Bundle certificate]
// Added for TELCODOCS-1827
include::modules/kmm-symbolic-links-for-in-tree-dependencies.adoc[leveloffset=+1]
@@ -64,7 +67,6 @@ include::modules/kmm-running-depmod.adoc[leveloffset=+2]
[role="_additional-resources"]
.Additional resources
* xref:../hardware_enablement/psap-driver-toolkit.adoc#driver-toolkit[Driver Toolkit]
include::modules/kmm-building-in-cluster.adoc[leveloffset=+2]

7
modules/kmm-example-module-cr.adoc
View File

@@ -81,7 +81,12 @@ spec:
<7> For any other kernel, build the image using the Dockerfile in the `my-kmod` ConfigMap.
<8> Optional.
<9> Optional: A value for `some-kubernetes-secret` can be obtained from the build environment at `/run/secrets/some-kubernetes-secret`.
<10> Optional: Avoid using this parameter. If set to `true`, the build is allowed to pull the image in the Dockerfile `FROM` instruction using plain HTTP.
<10> This field has no effect. When building kmod images or signing kmods within a kmod image,
you might sometimes need to pull base images from a registry that serves a certificate signed by an
untrusted Certificate Authority (CA). In order for KMM to trust that CA, it must also trust the new CA
by replacing the cluster's CA bundle.
+
See "Additional resources" to learn how to replace the cluster's CA bundle.
<11> Optional: Avoid using this parameter. If set to `true`, the build will skip any TLS server certificate validation when pulling the image in the Dockerfile `FROM` instruction using plain HTTP.
<12> Required.
<13> Required: A secret holding the public secureboot key with the key 'cert'.