Some Background: https://tracker.ceph.com/issues/64213 In particular, the python cryptography module uses PyO3 and on some versions of python, Ceph, and a new enough cryptography module the mgr may fail to start certain modules with an error like: PyO3 modules may only be initialized once per interpreter process A few of us have been looking into the problem and have come up with a workaround for the Ceph dashboard. The dashboard makes occasional use of cryptography and other libraries that also use cryptography. However, this use is fairly easy to encapsulate and not called to frequently. The cephadm module uses a ssh library that more heavily uses cryptography and is the module that will have direct access. That leaves two other modules that make use of cryptography. The 'rook' module and 'k8sevents' module. Speaking with some of the other Ceph developers we think that the 'rook' module is being used actively on rook deployments to enable the dashboard when orchestrated with rook. However, we are unsure if anyone is using the 'k8sevents' module at all. --- To help us better understand the status of the k8sevents module we'd like to ask the community if anyone is successfully using the k8sevents module. This will help us understand if this module is something we might be able to ultimately remove. Note that only one module of either k8sevents and rook could run on systems with newer cryptography libraries - so if we kept both we'd have to figure out a way to make the two modules that use kubernetes libraries compatible - and that may be complicated. To summarize: please let us know if you are using the k8sevents module, that it works for you and accomplishes something useful. Feel free to also let us know if you're using rook and the 'rook' module with-or-without the k8smodule. Thanks!