Support volumeGroup as source

[matancarmeli7]

Add Support to volumeGroup as a source, by adding replicationSource object which is replacing volumeID and can handle volumeID or VolumeGroupID as a source.

Signed-off-by: matancarmeli7 [email protected]

[nixpanic]

This PR adds a dependency on functionalities from the IBM Volume Group Controller. I do not think that is what we want in this project. We need to be storage provider agnostic, and only consume the protocol from the CSI-Addons Spec and use the standard Kubernetes API. If there is a dependency on a storage provider, other storage providers will have difficulties in implementing the required functionality.

Would it be possible to use the upcoming VolumeGroupSnapshot KEP-3476 for this? Or maybe something that works in a similar way, which could be added to the CSI-Addons Spec?

Ideally the features that are available in CSI-Addons will get proposed for the CSI Spec in the future.

[nixpanic]

@mergifyio rebase

[mergify[bot]]

rebase

✅ Branch has been successfully rebased

[nixpanic]

VolumeGroup and VolumeGroupContent are not types we like to expose to users. VolumeGroupReplication uses a label-selector instead, which then resolves into a list for VolumeGroupReplicationContent.