Moritz Wanzenböck

I'd really like to not have to reimplement a DaemonSet, but there are a few edge cases that I believe can't be fixed with a normal daemonset. On the top...

@alexzhc Do you know anything about that?

Still seems to be an issue. Sadly, I'm not sure how this works on the daocloud side (maybe @alexzhc can jump in?). I'm guessing someone has to manually copy the...

Nice work. I'll try to take a closer look at the project soon. One of the things I'd like to make sure is that this project does: * Work with...

> only change is that PV has hardcoded nodeAffinity. BTW, not really related to the issue at hand, but have you looked into the "advanced" access policy patterns: https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-kubernetes-params-allow-remote-volume-access Using...

So, we had a bit of an internal discussion, and the consensus is: yes, we want to support such a scheduler plugin. @kvaps in https://github.com/piraeusdatastore/piraeus-operator/pull/269#issuecomment-1038971113 you indicated you would be...

Moving forward with this, I'd say we fork your existing repo (we can request "detaching" the fork later, if needed). After we set up all the images, we add a...

Please change it to piraeusdatastore

Just realized I'm not an owner in this org, so I can't add you, either :upside_down_face: If you give me permissions to your own repo, I can initiate the transfer,...

Still had to fork it. maybe only the owner can trigger the transfer? :shrug: https://github.com/piraeusdatastore/linstor-scheduler-extender I'll see about detaching the fork and adding you as a collaborator