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 custom s3 endpoint #1454
Comments
We already have a bunch of drivers which are based on the S3 API (Google Cloud Storage, Aurora Objects, DigitalOcean Spaces, etc.) so it probably shouldn't be too hard to add a new S3 based provider driver for ceph-s3. |
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue. |
@puneetloya @Kami any news regarding this issue? I need to use cassandra medusa which uses libcloud storage on a minio object storage |
@DrissiReda As per my comment above - I don't think it should take much work for to add support for custom endpoints as we already have other drivers such as Google Storage based on the S3 one. I don't have access to any minio cluster to test it myself though. I guess I could try spinning it on minikube, but no idea when I'll get a chance to do that. |
I've used MinIO docker image to test it. I haven't done any extensive testing, but the basic operations I tested seem to work fine. |
Feature Request
Do you support or plan to support custom s3 endpoint? So that we can use providers like minio/ceph-s3
The text was updated successfully, but these errors were encountered: