SRO to KMMO transition

[Quentin Barrand]

Hello SIG Node,

At a recent meeting [1], we announced our plan of transitioning from the Special Resource Operator (SRO) to the Kernel Module Management Operator (KMMO) for the management of out-of-tree kernel modules and device plugins. We intend to promote KMMO as a SIG Node project in lieu of SRO and are looking into renaming the existing (empty) repository [2] and Slack channel [3].

KMMO has a reduced scope compared to that of SRO and thus requires much less privileges. We have put together a document [4] that hopefully clarifies the reasoning behind the new approach and the differences between the two projects.

I am happy to answer any question you might have on this topic.

Thanks!

Quentin

[1] https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit#heading=h.agoxhh8ulpv6

[2] https://github.com/kubernetes-sigs/special-resource-operator

[3] https://kubernetes.slack.com/archives/C037RE58RED

[4] https://docs.google.com/document/d/1QqTUI2SGn4MopcS-vUZYmp_vn21wNbHPon26iHgejBg/edit?usp=sharing

--

Quentin Barrand
Senior Software Engineer, Ecosystems Engineering
Products & Technologies Group, Red Hat
Mobile: +41 79 191 42 34

[Dawn Chen]

Quentin,

Somehow I cannot comment on the transition doc you shared above. The plan lgtm.

Thanks,

Dawn

> --
> You received this message because you are subscribed to the Google Groups "kubernetes-sig-node" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-node/CAAvQm7fPf4n6suhC-4Do8hCBCnHGYOWoJEKJvc0TZgfQCqDm1A%40mail.gmail.com.