k8s 1.12.1 的坑和解决pull 镜像:gcr.io 被墙，需要 pull 自己的镜像，然后改 tag。具体需要 pull 哪些镜像呢，kubeadm config images 可查看提示没权限：kubeadm reset 重复安装的时候，.kube 文件夹不会清空，但 key 已经重新生成了，所有会key secret 不匹配。解决办法是清空 .kube 目录，然后将 /etc/kubernetes/kube-admin.json 拷贝过来corednspending,network not ready:安装对应版本的 flannel。kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/master/Documentation/kube-flannel.yml1 node(s) had taints that the pod didn’t tolerate:默认 k8s 不允许往 master 节点装东西，强行设置下允许：kubectl taint nodes –all node-role.kubernetes.io/master-azure xxx:kubelet 自己的 bug, 无视The connection to the server localhost:8080 was refused :sudo cp /etc/kubernetes/admin.conf $HOME/sudo chown $(id -u):$(id -g) $HOME/admin.confexport KUBECONFIG=$HOME/admin.confhelm 没权限That’s because you don’t have permission to deploy tiller, add an account for it:kubectl create serviceaccount –namespace kube-system tiller serviceaccount “tiller” createdkubectl create clusterrolebinding tiller-cluster-rule –clusterrole=cluster-admin –serviceaccount=kube-system:tiller clusterrolebinding “tiller-cluster-rule” createdkubectl patch deploy –namespace kube-system tiller-deploy -p ‘{“spec”:{“template”:{“spec”:{“serviceAccount”:“tiller”}}}}’ deployment “tiller-deploy” patchedThen run below to check it :helm listhelm repo update