-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support volumeGroup as source #302
base: main
Are you sure you want to change the base?
Support volumeGroup as source #302
Conversation
d065c8a
to
c1f51c0
Compare
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. |
834196a
to
f9089fe
Compare
@Mergifyio rebase |
✅ Branch has been successfully rebased |
f9089fe
to
91772b5
Compare
go.mod
Outdated
@@ -17,7 +18,7 @@ require ( | |||
google.golang.org/grpc/cmd/protoc-gen-go-grpc v1.3.0 | |||
google.golang.org/protobuf v1.30.0 | |||
k8s.io/api v0.26.3 | |||
k8s.io/apimachinery v0.26.3 | |||
k8s.io/apimachinery v0.27.1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
operator-sdk does not like this update. Can you prevent this change?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes I saw, we need to downgrade it first in vg repo, I will do it and will update here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
Signed-off-by: matancarmeli7 <matan.carmeli7@gmail.com>
727f51b
to
6dae44d
Compare
Add Support to
volumeGroup
as a source, by addingreplicationSource
object which is replacingvolumeID
and can handlevolumeID
orVolumeGroupID
as a source.Signed-off-by: matancarmeli7 matan.carmeli7@gmail.com