Skip to content

Commit 454b191

Browse files
authored
Merge pull request #212 from BenTheElder/debugging-hint
add a debugging hint for GCP block
2 parents a269dd6 + 0d4aee0 commit 454b191

File tree

1 file changed

+13
-0
lines changed

1 file changed

+13
-0
lines changed

docs/debugging.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,17 @@ The registry.k8s.io is a Kubernetes container images registry that behaves gener
44

55
When you are debugging issues, make sure you run these commands on the node that is attempting to run images. Things may be working fine on your laptop, but not on the Kubernetes node.
66

7+
<!--TODO: identify what this looks like on s3 etc.-->
8+
> **Note**
9+
>
10+
> If you see a [403 error][http-403] like `Your client does not have permission to get URL`,
11+
> this error is not specific to the Kubernetes project / registry.k8s.io and
12+
> you need to work with your cloud vendor / service provider to get unblocked
13+
> by GCP.
14+
>
15+
> Please file an issue with your provider, the Kubernetes project does not
16+
> control this and it is not specific to us.
17+
718
## Verify DNS resolution
819

920
You may use the `dig` or `nslookup` command to validate DNS resolution of the registry.k8s.io domain or any domain it references. For example, running `dig registry.k8s.io` should return an answer that contains:
@@ -116,3 +127,5 @@ Mar 17 11:33:05 kind-control-plane containerd[224]: time="2023-03-17T11:33:05.19
116127
- https://github.com/kubernetes-sigs/kind/issues/1895#issuecomment-1468991168
117128
- https://github.com/kubernetes/registry.k8s.io/issues/174#issuecomment-1467646821
118129
- https://github.com/kubernetes/registry.k8s.io/issues/154#issuecomment-1435028502
130+
131+
[http-403]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403

0 commit comments

Comments
 (0)