Hello
Kubernetes Community,
Kernel
Module Management (KMM) operator v2.4.0 has been released and is
now available.
## Main new features
* Support for loading a device-plugin for an in-tree driver.
KMM can now only set a device-plugin for an already loaded, in-tree
driver, in the `Module`.
* Added an init-container to the device-plugin.
Allows setup validation before running the device plugin.
* Operator configuration will now persist operator upgrades.
Custom configuration for the operator via a configMap will now
persist to the next KMM version in case on an upgrade.
## Additional enhancements
* The operator is now pulling and checking images existence using
the cluster's container-runtime.
* KMM can now be installed on worker nodes, when control-plane nodes
aren't available, without the need to artificially label the worker
nodes as "control-plane".
* Reduce significantly the number of events we had to one of the
internal controller (NMC)
* Removed a service duplication (generated by OLM) for the webhook
deployment.
## Bug Fixes
* Fixed a bug when KMM was not re-loading the kmod when a reboot was
very fast (and the kube-api was not noticing that the node even went
down).
* Fixed a bug that the NMC CR was inheriting tolerations that were
not set in the Module
* Fixed a bug in which a failing worker-pod was hanging forever if
its Module was deleted.
More
details can be found on the release page [0].
Issues
can be reported on GitHub [1].
Please
join the KMM community on #sig-node-kmm [2] on Slack.
Thank
you,
Yoni
Bettan, on behalf of the KMM team
[1]: https://github.com/kubernetes-sigs/kernel-module-management/issues
[2]: https://kubernetes.slack.com/archives/C037RE58RED
--
Yoni Bettan
Senior Software Engineer, Ecosystems Engineering
Products & Technologies Group, Red Hat