kubeadm安装kubernetes(calico)
声明:接上一篇博客kubeadm安装kubernetes(flannel)
环境等都是一样，只是换了CNI而已,相关环境请参考kubeadm安装kubernetes(flannel)
1.calico官网描述
自行下载 calico.yaml文件
[root@master kubernetes]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
etcd-master 1/1 Running 0 2h
kube-apiserver-master 1/1 Running 0 2h
kube-controller-manager-master 1/1 Running 0 2h
kube-dns-692378583-1h70j 3/3 Running 3 2h
kube-proxy-2gzvq 1/1 Running 0 1h
kube-proxy-31lrc 1/1 Running 0 1h
kube-proxy-3rk7z 1/1 Running 0 2h
kube-scheduler-master 1/1 Running 0 2h[root@slave ~]# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
quay.io/calico/node v1.3.0 1948433a7679 5 days ago 256.1 MB
gcr.io/google_containers/kube-proxy-amd64 v1.6.6 b01133efa4f0 7 days ago 109 MB
quay.io/calico/cni v1.9.1 2902c3f3337e 11 days ago 70.82 MB
quay.io/calico/kube-policy-controller v0.6.0 b0d769544ab9 6 weeks ago 22.73 MB
gcr.io/google_containers/pause-amd64 3.0 99e59f495ffa 13 months ago 746.9 kB
gcr.io/google_containers/etcd 2.2.1 ef5842ca5c42 20 months ago 28.19 MB[root@master kubernetes]# kubectl apply -f http://docs.projectcalico.org/v2.3/getting-started/kubernetes/installation/hosted/kubeadm/1.6/calico.yaml
configmap "calico-config" created
daemonset "calico-etcd" created
service "calico-etcd" created
daemonset "calico-node" created
deployment "calico-policy-controller" created
clusterrolebinding "calico-cni-plugin" created
clusterrole "calico-cni-plugin" created
serviceaccount "calico-cni-plugin" created
clusterrolebinding "calico-policy-controller" created
clusterrole "calico-policy-controller" created
serviceaccount "calico-policy-controller" created[root@master kubernetes]# kubectl get nodes
NAME STATUS AGE VERSION
master Ready 2h v1.6.6
slave Ready 1h v1.6.6
slave1 Ready 1h v1.6.6
[root@master kubernetes]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
calico-etcd-shwp0 1/1 Running 0 1m
calico-node-3kgzq 2/2 Running 0 57s
calico-node-hdqr2 2/2 Running 0 57s
calico-policy-controller-1324707180-wkr0m 1/1 Running 0 57s
etcd-master 1/1 Running 0 2h
kube-apiserver-master 1/1 Running 0 2h
kube-controller-manager-master 1/1 Running 0 2h
kube-dns-692378583-1h70j 3/3 Running 3 2h
kube-proxy-2gzvq 1/1 Running 0 1h
kube-proxy-31lrc 1/1 Running 0 1h
kube-proxy-3rk7z 1/1 Running 0 2h
kube-scheduler-master 1/1 Running 0 2h[root@master kubernetes]# kubectl create -f dashboard.yaml
serviceaccount "kubernetes-dashboard" created
clusterrolebinding "kubernetes-dashboard" created
deployment "kubernetes-dashboard" created
service "kubernetes-dashboard" created[root@master kubernetes]# kubectl get pods -n kube-system
NAME READY STATUS RESTARTS AGE
calico-etcd-shwp0 1/1 Running 0 4m
calico-node-3kgzq 2/2 Running 0 4m
calico-node-hdqr2 2/2 Running 0 4m
calico-policy-controller-1324707180-wkr0m 1/1 Running 0 4m
etcd-master 1/1 Running 0 2h
kube-apiserver-master 1/1 Running 0 2h
kube-controller-manager-master 1/1 Running 0 2h
kube-dns-692378583-1h70j 3/3 Running 3 2h
kube-proxy-2gzvq 1/1 Running 0 1h
kube-proxy-31lrc 1/1 Running 0 1h
kube-proxy-3rk7z 1/1 Running 0 2h
kube-scheduler-master 1/1 Running 0 2h
kubernetes-dashboard-2039414953-8lsvq 1/1 Running 0 2m
end