Andrei Kvapil

piraeus-ha-controller updated to v1.1.0, PR rebased

Also shouldn't we move such information into USAGE.md ?

BTW, we deploy piraeus-operator and all CRs into the same namespace, we don't use any finalizers in deckhouse, to have an ability simple remove whole namespace more info and patch...

Just faced with the same issue now, you can face with this any time when nodes have no drbd-utils installed: ``` # dpkg-query -S /etc/multipath/conf.d/drbd.conf drbd-utils: /etc/multipath/conf.d/drbd.conf ```

Also the current implementation might be updated to generate patches locally using Helm: eg the following [values](https://github.com/piraeusdatastore/piraeus-operator/blob/master/examples/rbac-proxy-values.yaml) should generate: ```diff diff --git a/charts/piraeus/templates/operator-controller.yaml b/charts/piraeus/templates/operator-controller.yaml index 25ac9fe..3ce0a8f 100644 --- a/charts/piraeus/templates/operator-controller.yaml +++...

Hey, I think the best idea is to try align to well-known design patterns. - For example CSI and its `CSINode` object is managed by csi-node-registrar from the node side:...

Well, the driver loader pod can be created by the daemonset controller as well. Since you want to use separate driver loader image for every OS, this is a little...

> Work with late binding. This is something that broke STORK when I last tried it. I.e. the scheduler gets called for a Pod which has an unbound volume claim,...

Sure. Let's do that. I'm already active CNCF contributor and signed CLA as well. Guide me for the further steps, please.

> https://github.com/deckhouse/linstor-scheduler-extender thats the right repo to fork, right? Both repos are identical. Hey, I can try to change owner of [my repo](https://github.com/kvaps/linstor-scheduler-extender). Which github organization should I choose, [piraeusdatastore](https://github.com/piraeusdatastore)...