-
Notifications
You must be signed in to change notification settings - Fork 13
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
helm install is getting "toomanyrequests: You have reached your pull rate limit" error #69
Comments
Is there any guidance on how to create and use a "secret" for a private registry where the bitnami/kubectl image can be stored? Fyre VM's consistently experience/fail with this error due to shared IP addresses. Any guidance on how to tweak the Helm charts to authenticate and pull from a private registry for that image? Please let us know! Tagging @podgek - we were attempting to assist Kieran Hippsley yesterday. |
This should probably be added to the known issues along with some instructions on how and what to update to use an alternative registry. |
Hi, Sorry we missed this. The correct way to fix this would be to specify an In the meantime, you could update the OpenShift global pull-secret, similar to the workaround posted in the runbook for Minikube. |
I followed the Minikube workaround to get past this. I'll try it a few more times to make sure it wasn't a fluke of timing, but thanks for the pointer! |
Hi @kdombros, @khippsley A new property has been added to the values file in 21.5.0 to handle the Docker Hub credentials. global:
hubPullSecret:
registry: 'https://index.docker.io/v1/'
secretName: ''
username: ''
password: '' You can use your Docker Hub password or access token in the If you have a DockerHub secret already created and would like to reuse it, set the Thank you for your support. If you have any further issues on this topic, feel free to reopen this issue or create a new one. Regards andreyzher |
Very helpful - thanks! |
My helm install failed with:
I used the following to get details on the pod: kubectl describe pod releasename-apps-create-ltpa-keys-xrdp5 - note the "toomanyrequests: You have reached your pull rate limit" error:
To try to get around that, I authenticated to Docker Hub, pulled and tagged "kubectl" image as just "ocp/kubectl:latest" and did:
docker push default-route-openshift-image-registry.apps-crc.testing/ocp/kubectl:latest
I then modified Helm Charts to look for "kubectl:latest" instead of "bitnami/kubectl:1.19", issued
helm push apps + helm repo update
and then tried it all again, but that also failed - note the "unauthorized: authentication required":
Question: it seems that one way or another, I need to authenticate to a registry so that the docker pull's can succeed. Please advise - thanks!
The text was updated successfully, but these errors were encountered: