如果能够看到如上输出信息 ， 则表示master节点初始化成功 。
根据提示创建kubectl：
[root@instance01 ~]# mkdir -p $HOME/.kube[root@instance01 ~]# cp -i /etc/kubernetes/admin.conf $HOME/.kube/config[root@instance01 ~]# chown $(id -u):$(id -g) $HOME/.kube/config[root@instance01 ~]# source <(kubectl completion bash)查看master状态：
[root@instance01 ~]# kubectl get nodesNAMESTATUSROLESAGEVERSIONinstance01Readymaster85sv1.18.6查看pod状态：
pod状态
可以看到coredns一直是ContainerCreating状态 ， 原因是Kubernetes官网有这样一段话：
install network
大体意思是部署一个容器网络接口（CNI）基于Pod的网络插件 ， 在安装网络之前 ， 群集DNS（CoreDNS）将不会启动 ， Calico是kubeadm项目执行e2e测试的唯一CNI插件 。
所以接下来 ， 我们需要在Kubernetes集群中部署Calico插件：
wget Calico官网有这样一句话：
If you are using pod CIDR 192.168.0.0/16, skip to the next step. If you are using a different pod CIDR with kubeadm, no changes are required - Calico will automatically detect the CIDR based on the running configuration. For other platforms, make sure you uncomment the CALICO_IPV4POOL_CIDR variable in the manifest and set it to the same value as your chosen pod CIDR.
意思是Calico插件默认使用的Pod是192.168.0.0/16这个IP地址段 ， 如果我们的Kubernetes集群也是使用的这个地址段 ， 则不用修改；否则 ， 我们需要根据实际情况修改calico.yaml文件中的CALICO_IPV4POOL_CIDR这个变量 。
上面我们在初始化master节点的时候 ， Pod使用的地址段是10.122.0.0/16 ， 所以这一步我们需要修改CALICO_IPV4POOL_CIDR为10.122.0.0/16 。
# The default IPv4 pool to create on startup if none exists. Pod IPs will be# chosen from this range. Changing this value after installation will have# no effect. This should fall within `--cluster-cidr`.- name: CALICO_IPV4POOL_CIDRvalue: "10.122.0.0/16"[root@instance01 ~]# kubectl apply -f calico.yamlconfigmap/calico-config createdcustomresourcedefinition.apiextensions.k8s.io/bgpconfigurations.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/bgppeers.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/blockaffinities.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/clusterinformations.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/felixconfigurations.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/globalnetworkpolicies.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/globalnetworksets.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/hostendpoints.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/ipamblocks.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/ipamconfigs.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/ipamhandles.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/ippools.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/kubecontrollersconfigurations.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/networkpolicies.crd.projectcalico.org createdcustomresourcedefinition.apiextensions.k8s.io/networksets.crd.projectcalico.org createdclusterrole.rbac.authorization.k8s.io/calico-kube-controllers createdclusterrolebinding.rbac.authorization.k8s.io/calico-kube-controllers createdclusterrole.rbac.authorization.k8s.io/calico-node createdclusterrolebinding.rbac.authorization.k8s.io/calico-node createddaemonset.apps/calico-node createdserviceaccount/calico-node createddeployment.apps/calico-kube-controllers createdserviceaccount/calico-kube-controllers created[root@instance01 ~]#