whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update kubeadm init output to latest (#12440)

Browse Source 
There is output of `kubeadm init` in create-cluster-kubeadm page.
But it is little old.
Some processes aren't included in it.
This update `kubeadm init` output to latest.
This commit is contained in:
atoato88
2019-02-01 06:17:51 +09:00
committed by Kubernetes Prow Robot
parent 883f43e36b
commit a7f0d9a713
1 changed files with 48 additions and 31 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/setup/independent/create-cluster-kubeadm.md
+48 -31
View File
@@ -153,52 +153,69 @@ The output should look like:
```none ```none
[init] Using Kubernetes version: vX.Y.Z [init] Using Kubernetes version: vX.Y.Z
[preflight] Running pre-flight checks [preflight] Running pre-flight checks
[kubeadm] WARNING: starting in 1.8, tokens expire after 24 hours by default (if you require a non-expiring token use --token-ttl 0) [preflight] Pulling images required for setting up a Kubernetes cluster
[certificates] Generated ca certificate and key. [preflight] This might take a minute or two, depending on the speed of your internet connection
[certificates] Generated apiserver certificate and key. [preflight] You can also perform this action in beforehand using 'kubeadm config images pull'
[certificates] apiserver serving cert is signed for DNS names [kubeadm-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.138.0.4] [kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[certificates] Generated apiserver-kubelet-client certificate and key. [kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[certificates] Generated sa key and public key. [kubelet-start] Activating the kubelet service
[certificates] Generated front-proxy-ca certificate and key. [certs] Using certificateDir folder "/etc/kubernetes/pki"
[certificates] Generated front-proxy-client certificate and key. [certs] Generating "etcd/ca" certificate and key
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki" [certs] Generating "etcd/server" certificate and key
[kubeconfig] Wrote KubeConfig file to disk: "admin.conf" [certs] etcd/server serving cert is signed for DNS names [kubeadm-master localhost] and IPs [10.138.0.4 127.0.0.1 ::1]
[kubeconfig] Wrote KubeConfig file to disk: "kubelet.conf" [certs] Generating "etcd/healthcheck-client" certificate and key
[kubeconfig] Wrote KubeConfig file to disk: "controller-manager.conf" [certs] Generating "etcd/peer" certificate and key
[kubeconfig] Wrote KubeConfig file to disk: "scheduler.conf" [certs] etcd/peer serving cert is signed for DNS names [kubeadm-master localhost] and IPs [10.138.0.4 127.0.0.1 ::1]
[controlplane] Wrote Static Pod manifest for component kube-apiserver to "/etc/kubernetes/manifests/kube-apiserver.yaml" [certs] Generating "apiserver-etcd-client" certificate and key
[controlplane] Wrote Static Pod manifest for component kube-controller-manager to "/etc/kubernetes/manifests/kube-controller-manager.yaml" [certs] Generating "ca" certificate and key
[controlplane] Wrote Static Pod manifest for component kube-scheduler to "/etc/kubernetes/manifests/kube-scheduler.yaml" [certs] Generating "apiserver" certificate and key
[etcd] Wrote Static Pod manifest for a local etcd instance to "/etc/kubernetes/manifests/etcd.yaml" [certs] apiserver serving cert is signed for DNS names [kubeadm-master kubernetes kubernetes.default kubernetes.default.svc kubernetes.default.svc.cluster.local] and IPs [10.96.0.1 10.138.0.4]
[init] Waiting for the kubelet to boot up the control plane as Static Pods from directory "/etc/kubernetes/manifests" [certs] Generating "apiserver-kubelet-client" certificate and key
[init] This often takes around a minute; or longer if the control plane images have to be pulled. [certs] Generating "front-proxy-ca" certificate and key
[apiclient] All control plane components are healthy after 39.511972 seconds [certs] Generating "front-proxy-client" certificate and key
[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace [certs] Generating "sa" key and public key
[markmaster] Will mark node master as master by adding a label and a taint [kubeconfig] Using kubeconfig folder "/etc/kubernetes"
[markmaster] Master master tainted and labelled with key/value: node-role.kubernetes.io/master="" [kubeconfig] Writing "admin.conf" kubeconfig file
[bootstraptoken] Using token: <token> [kubeconfig] Writing "kubelet.conf" kubeconfig file
[bootstraptoken] Configured RBAC rules to allow Node Bootstrap tokens to post CSRs in order for nodes to get long term certificate credentials [kubeconfig] Writing "controller-manager.conf" kubeconfig file
[bootstraptoken] Configured RBAC rules to allow the csrapprover controller automatically approve CSRs from a Node Bootstrap Token [kubeconfig] Writing "scheduler.conf" kubeconfig file
[bootstraptoken] Creating the "cluster-info" ConfigMap in the "kube-public" namespace [control-plane] Using manifest folder "/etc/kubernetes/manifests"
[control-plane] Creating static Pod manifest for "kube-apiserver"
[control-plane] Creating static Pod manifest for "kube-controller-manager"
[control-plane] Creating static Pod manifest for "kube-scheduler"
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"
[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s
[apiclient] All control plane components are healthy after 31.501735 seconds
[uploadconfig] storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
[kubelet] Creating a ConfigMap "kubelet-config-X.Y" in namespace kube-system with the configuration for the kubelets in the cluster
[patchnode] Uploading the CRI Socket information "/var/run/dockershim.sock" to the Node API object "kubeadm-master" as an annotation
[mark-control-plane] Marking the node kubeadm-master as control-plane by adding the label "node-role.kubernetes.io/master=''"
[mark-control-plane] Marking the node kubeadm-master as control-plane by adding the taints [node-role.kubernetes.io/master:NoSchedule]
[bootstrap-token] Using token: <token>
[bootstrap-token] Configuring bootstrap tokens, cluster-info ConfigMap, RBAC Roles
[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: CoreDNS
[addons] Applied essential addon: kube-proxy [addons] Applied essential addon: kube-proxy
Your Kubernetes master has initialized successfully! Your Kubernetes master has initialized successfully!
To start using your cluster, you need to run (as a regular user): To start using your cluster, you need to run the following as a regular user:
mkdir -p $HOME/.kube mkdir -p $HOME/.kube
sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config sudo cp -i /etc/kubernetes/admin.conf $HOME/.kube/config
sudo chown $(id -u):$(id -g) $HOME/.kube/config sudo chown $(id -u):$(id -g) $HOME/.kube/config
You should now deploy a pod network to the cluster. You should now deploy a pod network to the cluster.
Run "kubectl apply -f [podnetwork].yaml" with one of the addon options listed at: Run "kubectl apply -f [podnetwork].yaml" with one of the options listed at:
http://kubernetes.io/docs/admin/addons/ https://kubernetes.io/docs/concepts/cluster-administration/addons/
You can now join any number of machines by running the following on each node You can now join any number of machines by running the following on each node
as root: as root:
kubeadm join --token <token> <master-ip>:<master-port> --discovery-token-ca-cert-hash sha256:<hash> kubeadm join <master-ip>:<master-port> --token <token> --discovery-token-ca-cert-hash sha256:<hash>
``` ```
To make kubectl work for your non-root user, run these commands, which are To make kubectl work for your non-root user, run these commands, which are