Skip to content
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

Merged
merged 1 commit into from
Jun 21, 2022

Conversation

mrsimonemms
Copy link
Contributor

@mrsimonemms mrsimonemms commented Jun 17, 2022

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

image

Related Issue(s)

Fixes #10697

How to test

Deploy with an Azure object store

Release Notes

[installer]: set minio azure image to last supported version

Documentation

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.
@mrsimonemms mrsimonemms marked this pull request as ready for review June 17, 2022 13:52
@mrsimonemms mrsimonemms requested a review from a team June 17, 2022 13:52
@github-actions github-actions bot added the team: delivery Issue belongs to the self-hosted team label Jun 17, 2022
Copy link
Contributor

@nandajavarma nandajavarma left a 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!

@roboquat roboquat merged commit c657f8d into main Jun 21, 2022
@roboquat roboquat deleted the sje/azure-minio-gateway branch June 21, 2022 10:45
@khurrambilalaurecon
Copy link

Hi,
I'm still receiving the same error that azure is not a minio sub-command.
I'm running Minio in Azure App service (Web App), passed startup file as "gateway azure". Any hints here?

image

@mrsimonemms
Copy link
Contributor Author

mrsimonemms commented Sep 22, 2022

@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 minio that is installed to your cluster

@khurrambilalaurecon
Copy link

Hi @mrsimonemms
I'm deploying minio docker image on Azure App service (Web app). Tried doing the same on Azure container instance as well, I pulled the latest docker image still received the above error, any thoguhts?

Thanks for the feedback.

@mrsimonemms
Copy link
Contributor Author

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.

@gitpod-io gitpod-io locked as off-topic and limited conversation to collaborators Sep 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-note size/S team: delivery Issue belongs to the self-hosted team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Minio gateway no longer supports Azure
4 participants