Description
Commit 0b70e7e
When I start the kubernetes master from projects/kubernetes and then run kubeadm-init.sh, neither of the kube-proxy or weave-net pods come up. In both the pod's logs there are errors complaining about files missing in /var/run/secrets/kubernetes.io/serviceaccount.
It looks to me like the kubelet is creating those files in the kubelet container, but the dockerd container is not able to see those same files.
If I go back to an earlier commit (e0bcac3) from over a month ago, both kube-proxy and weave-net can come up fine and when I look in the dockerd container, it can see the same kubernetes secrets mounts as in the kublet container.
Steps to reproduce the issue:
cd projects/kubernetesmake build-vm-images./boot.shctr exec --tty kubelet ashkubeadm-init.shkubectl --namespace=kube-system get pods- Repeat step 6 until the kube-proxy and weave-net pods to go to Error or CrashLoopBackOff state
kubectl --namespace=kube-system logs kube-proxy-7wdtn ;# Replace with your actual value from step 6- Look for a complaint in the output about
/var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directory
kubectl --namespace=kube-system logs weave-net-wqt0m weave ;# Replace with your actual value from step 6- Look for a complaint in the output about
/var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
df -h | grep secret and notice this kubelet container has two tmpfs mounts for each of weave-net and kube-proxyexit ;# to leave the kubelet containerctr exec docker df -h | grep secret and notice there is no outputctr exec docker docker ps -a and look for the container id for a kube-proxy instancectr exec docker docker inspect <containerid from previous step> | grep secret and notice the source of the mount is the same path as the tmpfs from step 12. But step 13 shows those tmpfs mounts are missing from the dockerd container. This is why steps 9 and 11 are complaining about no such file or directory.
Describe the results you received:
Neither the weave-net nor the kube-proxy pods came up due to the missing secrets mount
Describe the results you expected:
The weave-net and the kube-proxy pods should have come up
Description
Commit 0b70e7e
When I start the kubernetes master from projects/kubernetes and then run kubeadm-init.sh, neither of the kube-proxy or weave-net pods come up. In both the pod's logs there are errors complaining about files missing in /var/run/secrets/kubernetes.io/serviceaccount.
It looks to me like the kubelet is creating those files in the kubelet container, but the dockerd container is not able to see those same files.
If I go back to an earlier commit (e0bcac3) from over a month ago, both kube-proxy and weave-net can come up fine and when I look in the dockerd container, it can see the same kubernetes secrets mounts as in the kublet container.
Steps to reproduce the issue:
cd projects/kubernetesmake build-vm-images./boot.shctr exec --tty kubelet ashkubeadm-init.shkubectl --namespace=kube-system get podskubectl --namespace=kube-system logs kube-proxy-7wdtn;# Replace with your actual value from step 6/var/run/secrets/kubernetes.io/serviceaccount/ca.crt: no such file or directorykubectl --namespace=kube-system logs weave-net-wqt0m weave;# Replace with your actual value from step 6/var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directorydf -h | grep secretand notice this kubelet container has two tmpfs mounts for each of weave-net and kube-proxyexit;# to leave the kubelet containerctr exec docker df -h | grep secretand notice there is no outputctr exec docker docker ps -aand look for the container id for a kube-proxy instancectr exec docker docker inspect <containerid from previous step> | grep secretand notice the source of the mount is the same path as the tmpfs from step 12. But step 13 shows those tmpfs mounts are missing from the dockerd container. This is why steps 9 and 11 are complaining about no such file or directory.Describe the results you received:
Neither the weave-net nor the kube-proxy pods came up due to the missing secrets mount
Describe the results you expected:
The weave-net and the kube-proxy pods should have come up