docker - Flannel fails in kubernetes cluster due to failure of subnet manager -
i running etcd
, kube-apiserver
, kube-scheduler
, , kube-controllermanager
on master node kubelet
, kube-proxy
on minion node follows (all kube binaries kubernetes 1.7.4):
# [master node] ./etcd ./kube-apiserver --logtostderr=true --etcd-servers=http://127.0.0.1:2379 --service-cluster-ip-range=10.10.10.0/24 --insecure-port 8080 --secure-port=0 --allow-privileged=true --insecure-bind-address 0.0.0.0 ./kube-scheduler --address=0.0.0.0 --master=http://127.0.0.1:8080 ./kube-controller-manager --address=0.0.0.0 --master=http://127.0.0.1:8080 # [minion node] ./kubelet --logtostderr=true --address=0.0.0.0 --api_servers=http://$master_ip:8080 --allow-privileged=true ./kube-proxy --master=http://$master_ip:8080
after this, if execute kubectl --all-namespaces
, kubectl nodes
, get
namespace name cluster-ip external-ip port(s) age default svc/kubernetes 10.10.10.1 <none> 443/tcp 27m name status age version minion-1 ready 27m v1.7.4+793658f2d7ca7
then, apply flannel follows:
kubectl apply -f kube-flannel-rbac.yml -f kube-flannel.yml
now, see pod created, error:
namespace name ready status restarts age kube-system kube-flannel-ds-p8tcb 1/2 crashloopbackoff 4 2m
when check logs inside failed container in minion node, see following error:
failed create subnetmanager: unable initialize inclusterconfig: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
my question is: how resolve this? ssl issue? step missing in setting cluster?
Comments
Post a Comment