Anton Leanenka

My opinion that we can use multiple controllers for every volume group if we need this by providing ENV variable with volume group name, the same can be done for...

If user will change this variable there will be a new controller that will manage another volume group.Yes,I agree that can break smth but if I create provisioner and controller...

So I've added the env variable with lvm volume group for controller and tried to reproduce the issue that you mentioned above. What I did: 1. Create controller deployment with...

I did the same in step 2 only env variable name was another and this new controller did nothing with existing pvc and pv. Will try with env variable csi-lvm...

4.Turned back to my initial setup and tried to edit my controller deployment with kubectl edit deployment and changed the volume group variable from test-vg to new-test-vg, old pod controller...

Please check my PR https://github.com/metal-stack/csi-lvm/pull/30, maybe I did smth wrong when I tested it. Let's discuss and find where I was wrong.

@majst01 did you have time to check ?

I mean the case if we edit vg name in controller deployment and controller should remove pv, did you check this ? if yes, can you share the results please.