I have 2 vms that run a kubernetes master and a slave node that i have setup locally. Till now everything was working fine but suddenly it started giving errors when I try to start the master with kubeadm init command.I have cpppied the error below.
shayeeb@ubuntu:~$ sudo kubeadm init [init] using Kubernetes version: v1.11.1 [preflight] running pre-flight checks I0718 11:04:57.038464 20370 kernel_validator.go:81] Validating kernel version I0718 11:04:57.038896 20370 kernel_validator.go:96] Validating kernel config [preflight/images] Pulling images required for setting up a Kubernetes cluster [preflight/images] This might take a minute or two, depending on the speed of your internet connection [preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull' [preflight] Some fatal errors occurred: [ERROR ImagePull]: failed to pull image [ exit status 1 [ERROR ImagePull]: failed to pull image [ exit status 1 [ERROR ImagePull]: failed to pull image [ exit status 1 [ERROR ImagePull]: failed to pull image [ exit status 1 [preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...` 5 Answers
You can also run following command rather than writing the yaml,
kubeadm init --kubernetes-version=1.11.0 --apiserver-advertise-address=<public_ip> --apiserver-cert-extra-sans=<private_ip> If you are using flannel network run following commad,
kubeadm init --kubernetes-version=1.11.0 --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=<public_ip> --apiserver-cert-extra-sans=<internal_ip> The latest version(v1.11.1) is not pulling. You can try specifying the version like
kubeadm config images pull --kubernetes-version=v1.11.0
The image seems to have been removed :
As a workaround, pull the latest available images and ignore pre flight errors
kubeadm config images pull --kubernetes-version=v1.11.0 kubeadm init [args] --ignore-preflight-errors=all I was getting similar error . Proxy was causing "kubeadm config images pull" to timeout.
Similar issue was mentioned in
And the below solution provided in the above worked for me
systemctl set-environment HTTP_PROXY=
systemctl set-environment HTTPS_PROXY=
systemctl restart containerd.service
2Try this approach as it is working:
You can create config.yaml file, for example
cat config.yaml apiVersion: kind: MasterConfiguration api: advertiseAddress: 10.44.70.201 networking: podSubnet: 192.168.0.0/16 kubernetesVersion: 1.11.0 and run kubeadm init --config=kubeadm-config.yaml
