基于https://my.oschina.net/hansonwang99/blog/2993870 该文章,有几个漏掉的部分,导致一些坑
一、master安完后,安装Pod网络 ,如,过Pod自动同步失败,在node节点没有改容器以下三个容器 也需在各node需手动安装,
docker pull mirrorgooglecontainers/kube-proxy:v1.13.1
docker pull mirrorgooglecontainers/pause:3.1
docker pull registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64
docker tag mirrorgooglecontainers/kube-proxy:v1.13.1 k8s.gcr.io/kube-proxy:v1.13.1
docker tag mirrorgooglecontainers/pause:3.1 k8s.gcr.io/pause:3.1
docker tag registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64 quay.io/coreos/flannel:v0.10.0-amd64
docker rmi mirrorgooglecontainers/kube-proxy:v1.13.1
docker rmi mirrorgooglecontainers/pause:3.1
docker rmi registry.cn-shenzhen.aliyuncs.com/cp_m/flannel:v0.10.0-amd64
二、k8s dashboard 也通过镜像安装
三、 代理方式进入 ,其他的方式都暂时未成功
建立dashboard-admin.yaml 参考 https://github.com/kubernetes/dashboard/wiki/Access-control#basic 最后
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: kubernetes-dashboard
labels:
k8s-app: kubernetes-dashboard
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system
启动 kubectl --kubeconfig ./admin.conf proxy --address=master 地址 --disable-filter=true
进入的web 面选择跳过