-
Notifications
You must be signed in to change notification settings - Fork 367
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
Deploy to Ceph-based S3 gateway #1079
Comments
@mfrancis95 thanks for the report! I am thinking of adding an option What do you think? |
That sounds great. I need the ability to choose just |
Oh, ok? I think I'm confused. How does it then know which bucket the upload should go to? In your original issue description you said:
... which made me thought you need Could you clarify? Is this just one single large bucket? How does it get to know which bucket you are referring to? |
The I'm just coming from my limited experience using |
I think what we are looking for here might be the option |
@mfrancis95 i have no idea if this is what you are looking for, but i have added #1083 ... would you like to try this out? |
gonna merge the PR, closing this. feel free to reopen if needed. |
Hi. I'm trying to deploy to a Ceph-based S3 gateway.
Let's say my endpoint is
https://myendpoint.com
and the bucket ismybucket
. The deployment tries to accessmybucket.myendpoint.com:443
and gets aFailed to open TCP connection
error because that name doesn't exist. The gateway is not set up to give buckets their own subdomains. Is there any way I can configure the deployment process to upload to justmyendpoint.com:443
?The actual way in which a bucket is accessed using this gateway would be
https://myendpoint.com/mybucket
, nothttps://mybucket.myendpoint.com
.The text was updated successfully, but these errors were encountered: