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
In a cluster deployed on Hetzner, after a cluster is deployed one of the compute nodes stays in NotReady state. From the node logs we can see:
Failed to create pod sandbox: rpc error: code = Unknown desc = failed to get sandbox image "registry.k8s.io/pause:3.9": failed to pull image "registry.k8s.io/pause:3.9": failed to pull and unpack image "registry.k8s.io/pause:3.9": failed to resolve reference "registry.k8s.io/pause:3.9": unexpected status from HEAD request to https://europe-west3-docker.pkg.dev/v2/k8s-artifacts-prod/images/pause/manifests/3.9: 403 Forbidden
I've tried to manually pull the images from the VM with and the result is the same 403 Forbidden:
I wasn't able to setup a HTTPS proxy, spend 2 days.
To use the Proxy it needs to handle HTTPS traffic on port 443 but also on 6443.
it also needs to handle HTTP traffic (which was the easy step that worked)
During the HTTPS proxy setup I stumbled upon random issues like 502 badgateway, SSL CONNECT errors or some TLS1.3 errors
You will also need a valid certificate I used the one for claudie.dev on cloudflare
This issue is related to: kubernetes/registry.k8s.io#261 and #783
In a cluster deployed on Hetzner, after a cluster is deployed one of the compute nodes stays in
NotReady
state. From the node logs we can see:I've tried to manually pull the images from the VM with and the result is the same 403 Forbidden:
How it differs from #783 is that the cluster was able do provision and spinup a node.
The text was updated successfully, but these errors were encountered: