Created
March 14, 2018 07:29
-
-
Save yuanying/c0128f9f250fc2c4ba4ec46d16a2059d to your computer and use it in GitHub Desktop.
kubeadm init log
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
root@ubuntu-master01:/home/ubuntu# kubeadm init | |
[init] Using Kubernetes version: v1.9.4 | |
[init] Using Authorization modes: [Node RBAC] | |
[preflight] Running pre-flight checks. | |
[WARNING FileExisting-crictl]: crictl not found in system path | |
[certificates] Generated ca certificate and key. | |
[certificates] Generated apiserver certificate and key. | |
[certificates] apiserver serving cert is signed for DNS names [ubuntu-master01 kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 172.18.10.84] | |
[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] Valid certificates and keys now exist in "/etc/kubernetes/pki" | |
[kubeconfig] Wrote KubeConfig file to disk: "admin.conf" | |
[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf" | |
[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf" | |
[kubeconfig] Wrote KubeConfig file to disk: "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 55.501737 seconds | |
[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace | |
[markmaster] Will mark node ubuntu-master01 as master by adding a label and a taint | |
[markmaster] Master ubuntu-master01 tainted and labelled with key/value: node-role.kubernetes.io/master="" | |
[bootstraptoken] Using token: 7c0767.e8467d0b00930f2e | |
[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: kube-dns | |
[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 --token 7c0767.e8467d0b00930f2e 172.18.10.84:6443 --discovery-token-ca-cert-hash sha256:839784bd665967b84c61eed98a797beb684d6cda716a07200d524b6d49cf1270 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment