From ef03e21f89a63afdec24668d40eebb6142e78a2c Mon Sep 17 00:00:00 2001 From: StephenJamesSmith Date: Wed, 1 May 2024 15:34:36 -0400 Subject: [PATCH] TELCODOCS-1825: QE review --- modules/kmm-unloading-kernel-module.adoc | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/modules/kmm-unloading-kernel-module.adoc b/modules/kmm-unloading-kernel-module.adoc index 2c8265f058..959ee4d0d9 100644 --- a/modules/kmm-unloading-kernel-module.adoc +++ b/modules/kmm-unloading-kernel-module.adoc @@ -16,8 +16,5 @@ You must unload the kernel modules when moving to a newer version or if they int ==== When unloading worker pods, KMM needs all the resources it uses when loading the kernel module. This includes the `ServiceAccount` referenced in the `Module` as well as any RBAC defined to allow privileged KMM worker Pods to run. It also includes any pull secret referenced in `.spec.imageRepoSecret`. -To avoid situations where KMM is unable to unload the kernel module from nodes: - -* Do not delete those resources while the `Module` resource is still present in the cluster in any state, including `Terminating`. -* Do not delete any namespace containing at least a `Module` resource. +To avoid situations where KMM is unable to unload the kernel module from nodes, make sure those resources are not deleted while the `Module` resource is still present in the cluster in any state, including `Terminating`. KMM includes a validating admission webhook that rejects the deletion of namespaces that contain at least one `Module` resource. ====