Stuck at validating version wow
changed it back to "gcr.io/google-containers" and re-ran. null_resource.k8sc1-node2 (remote-exec): Pulling repository docker.io/googlecontainers/hyperkube-amd64 null_resource.k8sc1-node4 (remote-exec): Error: image googlecontainers/hyperkube-amd64 not found null_resource.k8sc1-node4 (remote-exec): Failed to docker pull hyperkube I was unable to deploy a version newer than v1.6.5, but this issue board answered a lot of my questions. My remaining question is, what do I do with old cluster versions? .phase3.run_addons=y .phase3.kube_proxy=y .phase3.dashboard=y .phase3.heapster=y .phase3.kube_dns=y After I had to install kubectl on the Master using - https://coreos.com/tectonic/docs/latest/tutorials/kubernetes/Used the fix provided by divyenpatel commented on Jan 24 $ kubectl uncordon kubernetes-master node "kubernetes-master" uncordoned You can enable scheduling permanently on the master node by setting --register-schedulable=true in /etc/systemd/system/kubelet.service. Tested the volume creation using - https://github.com/kubernetes/examples/blob/master/staging/volumes/vsphere/README.md#storage-class Hope that helps someone else out!But both of these tools are actually online installers of Windows 10 which download Windows 10 ISO files from Microsoft servers in background and if something goes wrong in the middle, you need to restart the whole process again and re-download the full ISO file of Windows 10.Many users have faced such kind of problems in downloading Windows 10 setup files using these tools.So, I am also curious as to what the roadmap is for supporting newer releases. Redid make config getting everything correct and using docker.io/cnastorage/k8s-ignition:v1.8-dev-release for the ignition image. make deploy created the cluster in under 3 minutes.