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

minio setup notebook needs updating #2670

Closed
ryandawsonuk opened this issue Nov 19, 2020 · 0 comments · Fixed by #2675
Closed

minio setup notebook needs updating #2670

ryandawsonuk opened this issue Nov 19, 2020 · 0 comments · Fixed by #2675
Labels
bug triage Needs to be triaged and prioritised accordingly

Comments

@ryandawsonuk
Copy link
Contributor

helm install minio stable/minio \
    --set accessKey=minioadmin \
    --set secretKey=minioadmin \
    --namespace minio-system

Gives Error: failed to download "stable/minio" (hint: running helm repo update may help). Need to reference specific helm repo in https://github.com/SeldonIO/seldon-core/blob/master/notebooks/minio_setup.ipynb and https://github.com/SeldonIO/seldon-core/blob/master/examples/minio_setup.ipynb

Can add stable with:

helm repo add stable https://kubernetes-charts.storage.googleapis.com
helm repo update

But it still fails and helm pull stable/minio gives Error: failed to fetch https://charts.helm.sh/stable/minio-5.0.33.tgz : 404 Not Found

Am on helm v3.2.4 and seems others have seen permutations of this. Could be the chart's versioning or related to the deprecating of the stable repo. We should now be using https://github.com/minio/charts. So

helm repo add minio https://helm.min.io/
helm install minio minio/minio \
    --set accessKey=minioadmin \
    --set secretKey=minioadmin \
    --namespace minio-system
@ryandawsonuk ryandawsonuk added bug triage Needs to be triaged and prioritised accordingly labels Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant