Moritz Wanzenböck

In general it's not save, as some resource reference each other in non-obvious ways. I can try to reproduce it internally, but I can't promise when I can get to...

FYI: we are working on a solution, as loading a cluster with many properties seems to take excessively long. It should be ready pretty soon.

@blampe If you want to give the new version a try, there is an updated image available at `quay.io/piraeusdatastore/piraeus-server:v1.20.0-rc.1`, or you can use the new [Piraeus Operator RC](https://github.com/piraeusdatastore/piraeus-operator/releases/tag/v1.10.0-rc.1)

Hmmm, you can scale down the `piraeus-operator` deployment, edit the controller deployment to run `tail -f /dev/null`, remove the `livenessProbe` and then exec into the new container, and manually start...

Looks like a bug (we had a few similar reports internally), but I could never reproduce the situation. > Also surprising was the list of topology keys included every node...

> Consider using [Kustomize](https://kustomize.io/) as the default deployment tool On that front, I can report that the [`v2` branch](https://github.com/piraeusdatastore/piraeus-operator/tree/v2) is already using kustomize, both as a way to deploy the...

The error message seems strange. Nothing has changed in regards to permissions in a while. A quick google search reveals that this message also happens if there is an inconsistency...

Anything relevant in the kernel logs (`dmesg` or `journalctl -t kernel`) on that issue?

Hmm, I see. I guess the issue is that during a failover event we leave the FS in a non-perfect state, and now it does not allow online resize. Unmounting...

Looks like a custom certificate for the remote endpoint is currently not implemented in LINSTOR. There might be a way this can be done by overriding the java cert store...