Kernel Module Management 2.0 upgrade from 1.1.x

Issue

When migrating from KMM 1.1.x to KMM 2.0, due to the architecture change for deploying out-of-tree kernel modules, it's possible downtime will need to be schedule as part of the upgrade process. This is due to the way the kernel modules are deployed and managed in the new architecture moving away from daemonsets, which constantly run, to deploying using the needed kernel module(s) using pods.