-
Notifications
You must be signed in to change notification settings - Fork 7
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
Allow for CSI provisioned volume or storage class as source #42
Conversation
5912953
to
41dc1d5
Compare
return fmt.Errorf("failed to update ReclaimPolicy for PV object %s: %v", pvc.Spec.VolumeName, err) | ||
} | ||
|
||
// retrieve and validate the volume name before starting the migration |
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.
i've reordered this to validate prior to mutating the resource
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.
@emosbaugh changes LGTM, update the readme for this support?
added documentation to the readme |
let's wait for #43 before merging |
@emosbaugh can you please just rebase on top of main, we just fix the ci after that we'll good to merge the pr |
c5071b9
to
f9f6570
Compare
rebased |
I understand it is not the intention of the project as clearly stated in the readme, but I found with this small change it is possible to migrate from CSI to CSI volumes.
Our use case is migrating from a flex driver storage class, to a temporary csi storage class, deleting the flex storage class, and migrating to a csi storage class with the same name as the original flex storage class.