search

luxas / kubeadm-workshop

Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring
MIT License
679 stars 190 forks source link

Image pull backoff kube-proxy #17

Closed codesnk closed 7 years ago

codesnk commented 7 years ago

Thanks for the detailed workshop writeup.

I get an error for the kube-proxy image after these steps:

kubectl -n kube-system set image daemonset/kube-proxy kube-proxy=luxas/kube-proxy:v1.7.0-beta.1

kube-system   etcd-shazdell                      1/1       Running            3          1h
kube-system   kube-apiserver-shazdell            1/1       Running            3          1h
kube-system   kube-controller-manager-shazdell   1/1       Running            3          1h
kube-system   kube-dns-3832805406-lnd0m          0/3       Pending            0          1h
kube-system   kube-proxy-p6551                   0/1       ImagePullBackOff   0          50m
kube-system   kube-scheduler-shazdell            1/1       Running            3          1h
luxas commented 7 years ago

@ShahNawazKhan Sure, just skip this step for now. I haven't had a chance to push that image yet...

Will probably be fixed tomorrow-ish :)

codesnk commented 7 years ago

Thanks for the quick reply @luxas. However, I am confused whether the mixed-arch cluster will work without this step/image. I am planning an amd64 master and ARM7 workers.

luxas commented 7 years ago

Now it should work as expected, pushed the image ;)