kubeadm安装kubernetes集群

darkpoon

[root@Docker-5 ~]# kubeadm init --kubernetes-version=v1.11.0 --pod-network-cidr=10.244.0.0/16 --apiserver-advertise-address=20.0.30.105　　[init] using Kubernetes version: v1.11.0
　　[preflight] running pre-flight checks
　　I0726 17:41:23.621027   65735 kernel_validator.go:81] Validating kernel version
　　I0726 17:41:23.621099   65735 kernel_validator.go:96] Validating kernel config
　　[WARNING Hostname]: hostname "docker-5" could not be reached
　　[WARNING Hostname]: hostname "docker-5" lookup docker-5 on 8.8.8.8:53: no such host
　　[preflight/images] Pulling images required for setting up a Kubernetes cluster
　　[preflight/images] This might take a minute or two, depending on the speed of your internet connection
　　[preflight/images] You can also perform this action in beforehand using 'kubeadm config images pull'
　　[kubelet] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
　　[kubelet] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
　　[preflight] Activating the kubelet service
　　[certificates] Generated ca certificate and key.
　　[certificates] Generated apiserver certificate and key.
　　[certificates] apiserver serving cert is signed for DNS names [docker-5 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 20.0.30.105]
　　[certificates] Generated apiserver-kubelet-client certificate and key.
　　[certificates] Generated sa key and public key.
　　[certificates] Generated front-proxy-ca certificate and key.
　　[certificates] Generated front-proxy-client certificate and key.
　　[certificates] Generated etcd/ca certificate and key.
　　[certificates] Generated etcd/server certificate and key.
　　[certificates] etcd/server serving cert is signed for DNS names [docker-5 localhost] and IPs [127.0.0.1 ::1]
　　[certificates] Generated etcd/peer certificate and key.
　　[certificates] etcd/peer serving cert is signed for DNS names [docker-5 localhost] and IPs [20.0.30.105 127.0.0.1 ::1]
　　[certificates] Generated etcd/healthcheck-client certificate and key.
　　[certificates] Generated apiserver-etcd-client certificate and key.
　　[certificates] valid certificates and keys now exist in "/etc/kubernetes/pki"
　　[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/admin.conf"
　　[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/kubelet.conf"
　　[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/controller-manager.conf"
　　[kubeconfig] Wrote KubeConfig file to disk: "/etc/kubernetes/scheduler.conf"
　　[controlplane] wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml"
　　[controlplane] wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml"
　　[controlplane] wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml"
　　[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml"
　　[init] waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests"
　　[init] this might take a minute or longer if the control plane images have to be pulled
　　[apiclient] All control plane components are healthy after 39.001159 seconds
　　[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
　　[kubelet] Creating a ConfigMap "kubelet-config-1.11" in namespace kube-system with the configuration for the kubelets in the cluster
　　[markmaster] Marking the node docker-5 as master by adding the label "node-role.kubernetes.io/master=''"
　　[markmaster] Marking the node docker-5 as master by adding the taints [node-role.kubernetes.io/master:NoSchedule]
　　[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "docker-5" as an annotation
　　[bootstraptoken] using token: g80a49.qghzuffg3z58ykmv
　　[bootstraptoken] configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials
　　[bootstraptoken] configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token
　　[bootstraptoken] configured RBAC rules to allow certificate rotation for all node client certificates in the cluster
　　[bootstraptoken] creating the "cluster-info" ConfigMap in the "kube-public" namespace
　　[addons] Applied essential addon: CoreDNS
　　[addons] Applied essential addon: kube-proxy
　　Your Kubernetes master has initialized successfully!
　　To start using your cluster, you need to run the following as a regular user:
　　mkdir -p $HOME/.kube
　　sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
　　sudo chown $(id -u):$(id -g) $HOME/.kube/config
　　You should now deploy a pod network to the cluster.
　　Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
　　https://kubernetes.io/docs/concepts/cluster-administration/addons/
　　You can now join any number of machines by running the following on each node
　　as root:
　　kubeadm join 20.0.30.105:6443 --token g80a49.qghzuffg3z58ykmv --discovery-token-ca-cert-hash sha256:8ae3e31892f930ba48eb33e96a2d86c0daf2a13847f8dc009e25e200a9cee6f6
　　[root@Docker-5 ~]#