Docker开发平台的构建(2)

Flag --external-etcd-endpoints has been deprecated, this flag will be removed when componentconfig exists
[kubeadm] WARNING: kubeadm
is in alpha, please do not use it for production clusters.
[preflight] Running pre
-flight checks
[preflight] WARNING: kubelet service
is not enabled, please run 'systemctl enable kubelet.service' [preflight] Starting the kubelet service [init] Using Kubernetes version: v1.5.1
[tokens] Generated token:
"e2e92d.d96382dcac25aa22"
[certificates] Generated Certificate Authority key and certificate.
[certificates] Generated API Server key and certificate
[certificates] Generated Service Account signing keys
[certificates] Created keys and certificates
in "/etc/kubernetes/pki"
[kubeconfig] Wrote KubeConfig file to disk:
"/etc/kubernetes/kubelet.conf"
[kubeconfig] Wrote KubeConfig file to disk:
"/etc/kubernetes/admin.conf"
[apiclient] Created API client, waiting
for the control plane to become ready
[apiclient] All control plane components are healthy after
22.501928 seconds
[apiclient] Waiting
for at least one node to register and become ready
[apiclient] First node
is ready after 0.509735 seconds
[apiclient] Creating a test deployment
[apiclient] Test deployment succeeded
[token
-discovery] Created the kube-discovery deployment, waiting for it to become ready
[token
-discovery] kube-discovery is ready after 3.503953 seconds
[addons] Created essential addon: kube
-proxy
[addons] Created essential addon: kube
-dns

Your Kubernetes master has initialized successfully
!

You should now deploy a pod network to the cluster.
Run
"kubectl apply -f [podnetwork].yaml" with one of the options listed at:
    http:
//kubernetes.io/docs/admin/addons/

You can now join any number of machines by running the following on each node:

kubeadm join
--token=e2e92d.d96382dcac25aa22 192.168.6.131

内容版权声明:除非注明,否则皆为本站原创文章。

转载注明出处:https://www.heiqu.com/14137.html