Moritz Wanzenböck

I see. That is indeed a very specific issue. I'll see if this can somehow be checked with openssl

Hmm, there seems to be some leftover volume data somewhere in the datastore. You can ask over at the https://github.com/LINBIT/linstor-server/ project or at the [LINBIT forums](https://forums.linbit.com/) for specific pointers.

Looks like you used the "openssl" method from [here](https://github.com/piraeusdatastore/piraeus-operator/blob/v2/docs/how-to/internal-tls.md#provision-keys-and-certificates-using-openssl) to create those certificates? If so, the issue is that those certificates only set a generic common name: ``` openssl req...

I'm wondering why it would try to load the system trust store: ``` tlshd[11]: System trust: Loaded 140 certificate(s). ``` But sometimes it loads the right certificates instead: ``` tlshd[12]:...

Just last week we added `linux-kbuild-*` in the debian containers: https://github.com/piraeusdatastore/piraeus/pull/145 From my tests this seems to be enough to fix building with the existing Operator on Debian.

> I was just thinking if there are no other cases like that, when kernel-headers demands on anything from /usr/lib? For now, Debian seem to be the only ones doing...

This seems to be handled for the most part by adding the linux-kbuild-* packages to the containers. There is also now https://piraeus.io/docs/v2/how-to/raspian/#configure-the-drbd-module-loader-for-raspberry-pi-os-raspian for more esoteric distributions.

That will be difficult. Why are your host names different between kubernetes and the host OS?

You still need at least a satellite running on the kubernetes workers. You can use the operator to connect to your existing cluster: https://github.com/piraeusdatastore/piraeus-operator/blob/v2/docs/how-to/external-controller.md

Well, you can start with setting up the Controller and external Satellites, including registering the satellites with `linstor node create`. Then, you can use the Operator to connect to the...