You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugging.md
+13Lines changed: 13 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -4,6 +4,17 @@ The registry.k8s.io is a Kubernetes container images registry that behaves gener
4
4
5
5
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.
6
6
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
+
7
18
## Verify DNS resolution
8
19
9
20
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
0 commit comments