-
Notifications
You must be signed in to change notification settings - Fork 168
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
Mount existing bucket and access the data already in the bucket #55
Comments
yes, mounting existing bucket and existing folder, that is what I am looking for |
Christian-TD
pushed a commit
to defrox/csi-s3
that referenced
this issue
Dec 7, 2021
@lynnmatrix @minkbear check this #60 |
We're using #60 , would definitely be happy to see it merged! |
It looks good to me |
Christian-TD
pushed a commit
to defrox/csi-s3
that referenced
this issue
Feb 1, 2022
…trox#55 chore: updated README.md
ctrox
added a commit
that referenced
this issue
Feb 2, 2022
feat: enable mounting an existing bucket #55
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One of my use case of csi-s3 is mounting existing bucket and access the data in it, anyone share the same use case with me?
Issue #14 propose a request to mount existing bucket, and PR #42 provided an implementation to meet this request, also the volume created by the solution in PR #42 will mount the root of existing bucket, which means it can access data already existed before the volume created.
@ctrox, your commit "Use volume ID as a prefix if the bucket is fixed in the storage class" will create new path for volume even if the bucket existed, so the volume can not access data already existed in the bucket.
@ctrox, is my use case suit for csi-s3? what's your suggestion?
The text was updated successfully, but these errors were encountered: