-
Notifications
You must be signed in to change notification settings - Fork 75
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
Cannot pull images from AWS EKS Cluster (Region eu-central1, Frankfurt) #245
Comments
@sebschlue Do you mind go through the debugging guide so we can get more informations about this issue you are facing ? What you provided is enough for us to properly investigate this issue. |
I will try some tests. First test:
|
Second test:
|
third test:
|
Last message just shows permission denied for writing the tarball. Did you get past that? |
Yes :) Now you can see the 403 at the end:
|
This works from my machine:
So it's not the blob at least, something between S3 and your host. Is it possible your environment has some restrictions on S3 access? Previously kubernetes/k8s.io#4214 (comment) |
Thanks a lot, will check it :) |
Okay, I did not yet figure out the root cause, but it's now clear that it is not a general issue but limited to my environment, so ticket can be closed. Thanks a lot for your help :) |
Is there an existing issue for this?
What did you expect to happen?
Image pull from registry.k8s.io should work but I simply get 403 Forbidden
Debugging Information
Normal Pulling 87s (x4 over 2m58s) kubelet Pulling image "registry.k8s.io/metrics-server/metrics-server:v0.6.3"
Warning Failed 86s (x4 over 2m57s) kubelet Failed to pull image "registry.k8s.io/metrics-server/metrics-server:v0.6.3": rpc error: code = Unknown desc = failed to pull and unpack image "registry.k8s.io/metrics-server/metrics-server:v0.6.3": failed to copy: httpReadSeeker: failed open: unexpected status code https://registry.k8s.io/v2/metrics-server/metrics-server/blobs/sha256:817bbe3f2e5179b5fa7dd4085c87aab1faaf9dc879e3b1d05796901a006f58ab: 403 Forbidden
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: