I've did this. It's because the kubelet is trying to downloading static pods (i.e. docker containers) from the internet. If you're using coreos, it's likely r

I've did this. It's because the kubelet is trying to downloading static pods (i.e. docker containers) from the internet. If you're using coreos, it's likely rkt is trying to download flannel (if you're using it) and the hyperkube container from the internet too. Good news, all this is configurable. Bad news, it's no longer really a turnkey solution. For the most part, bootstrapping kubernetes just from the hyperkube isn't that difficult. You just have to change the static manifests for the apiserver, controller, scheduler and the proxy to point to your private registry. You then need to change the kubelet(s) to use a private registry for the --pod-infra-container-image. This should probably be enough to get you up and running. With kubeadm (1.8+) you can use imageRepository: <private-registry> in kubeadm config file.