-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[installer]: set minio azure image to last supported version #10717
Conversation
Azure support has been removed from the latest version of minio gateway. If Azure is selected as the object store, this uses the last supported version of Minio gateway with Azure support.
1a0fdd2
to
da9a7a8
Compare
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.
Adding this change to the test environment fixes the issues!
@khurrambilalaurecon what version of Gitpod are you using? This has been fixed for some time so I'm hopeful you're using an old version Also, please check the version of |
Hi @mrsimonemms Thanks for the feedback. |
Are you running Gitpod? I don't mind helping, but this is the thread for Gitpod, not the Minio Gateway application - really, you should be on that project's issue page. For the record, the problem is that you're running the latest Docker image - they removed it so you need to use the last version that has it in. Go through this PR's files and you'll see that I've changed to the last support version - use that and you'll be grand. |
Description
Azure support has been removed from the latest version of Minio gateway. If Azure is selected as the object store, this uses the last supported version of Minio gateway with Azure support.
This also means that the Azure gateway won't receive any updates. I think this is an acceptable compromise on the basis that the gateway and the object storage endpoints are separate binaries/codebases anyway. This will need a better fix in time (probably adding Azure as a native storage option in the
content-service
) as there will undoubtedly be divergences between the Helm chart and image. However, this will solve the problem in the short-term.Proof that it's uploading to the blob store
Related Issue(s)
Fixes #10697
How to test
Deploy with an Azure object store
Release Notes
Documentation