Moritz Wanzenböck

I think you may have needed to restart the `piraeus-operator-controller-manager` Pod. It only loads the config map once on start-up. In normal operation the file will only change when also...

It looks like the Operator could not complete the full reconciliation of the `LinstorCluster` resource. Can you check the `.status` of the `LinstorCluster` resource?

The issue is probably that we only try to mount `/usr/src` from the host. I think on debian-systems there are some scripts that are moved into a separate directory and...

🤔 I'm wondering if it would be simpler to install the `drbd-dkms` package directly on the host.

Yeah. You might need to pretend to be "proxmox-8" because the public bookworm repos do not have the dkms package installed.

The issue is notably not with the normal upstream bookworm (which works just fine), but with the Raspbian variant, which has a custom kernel. For the normal bookworm image, we...

Can you check the events on the PVC? If you have a snapshot, linstor-csi shouldn't actually try to delete the RD. Instead it will delete the resource manually (so `linstor...

Usually you would set up monitoring using the `linstor-cluster` chart. There you can set `monitoring.enabled=true` and this will create the ServiceMonitor, PodMonitor, PrometheusRule and grafana dashboard. Not sure how this...

Hmm, does the container log to the ephemeral storage of a container? Other than that, I wouldn't know what storage they'd use?

I guess we could add something here: https://github.com/piraeusdatastore/piraeus-operator/blob/master/examples/resource-requirements.yaml This is also relevant for v2. I thought the operator-sdk explicitly recommended to _not_ set any requests and limits, but it looks...