-
-
Notifications
You must be signed in to change notification settings - Fork 329
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
403 - Forbidden ErrImagePull #451
Comments
Hello, please try fixing the version of the hetzner csi, see in the kube.tf.example for the right vqariable. That will take care of GitHub rate limit issues. If that does not work, please share you kube.tf file here without sensitive values. |
Ok i found a solution, i don't understand it but "it work" I don't think the problem is related to the terraform-hcloud-kube-hetzner but it's probably linked to hetzner itself. When i tried to pull image with this command on my problematic node:
I got this :
I had two different images with this problem, but then one of the images was successfully pulled. I think the issue may be with Hetzner or with the public IP of my node being blacklisted, but I'm not sure. The following script worked for me:
I wish I could provide a more accurate answer, but it seems that my IP may have been banned on some nodes of the gcr.io registry. By repeatedly forcing requests, I was able to find a registry node that did not have my IP banned. This allowed me to successfully pull the image. |
Very interesting experience @alexisgardin. Thanks for sharing! First time I see this issue honestly. You were right, hetzner_csi_version is for the CSI YAML file itself and had nothing to do with the image. Honestly, I replied from my phone in a hurry, I did not want to wait more because the ticket was two days already. I should've read the issue better. I ended up learning a lot from you, crictl seems super useful, never actually knew what it was, but now its use case is clear. The fact that it failed even after applying the Last but not least, this makes me think of the usefulness of supporting an in-cluster registry one day like Harbor. If you have thoughts on this, please don't hesitate. |
Hi, I'm still seeing this with a fresh install. Events:
|
@pbnsilva Something seems up with gcr.io, for now, I suggest you use the |
One of my node have this error bellow :
This is very simillar with this issue : #442
What i have tried :
registry.k8s.io
For this i used the kube.tf.example with the updated config here :
Every time I created a cluster, there was only one node that was in error. The other two had no problem. In the 1st case, it was a worker node and in the 2nd test it was the control pane node.
Hope you can help me with this issue !
The text was updated successfully, but these errors were encountered: