kubernetes V1.10.4 集群部署 (手动生成证书)

死siua11

# kubeadm init --config config.yaml　　
[init] Using Kubernetes version: v1.10.4
　　
[init] Using Authorization modes: [Node RBAC]
　　
[preflight] Running pre-flight checks.
　　
        [WARNING FileExisting-crictl]: crictl not found in system path
　　
Suggestion: go get github.com/kubernetes-incubator/cri-tools/cmd/crictl
　　
[preflight] Starting the kubelet service
　　
[certificates] Using the existing ca certificate and key.
　　
[certificates] Using the existing apiserver certificate and key.
　　
[certificates] Using the existing apiserver-kubelet-client certificate and key.
　　
[certificates] Using the existing sa key.
　　
[certificates] Using the existing front-proxy-ca certificate and key.
　　
[certificates] Using the existing front-proxy-client certificate and key.
　　
[certificates] Valid certificates and keys now exist in "/etc/kubernetes/pki"
　　
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/admin.conf"
　　
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/kubelet.conf"
　　
[kubeconfig] Using existing up-to-date KubeConfig file: "/etc/kubernetes/controller-manager.conf"
　　
[kubeconfig] Using existing up-to-date KubeConfig file: "/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"
　　
[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 15.506913 seconds
　　
[uploadconfig] Storing the configuration used in ConfigMap "kubeadm-config" in the "kube-system" Namespace
　　
[markmaster] Will mark node k8s01 as master by adding a label and a taint
　　
[markmaster] Master k8s01 tainted and labelled with key/value: node-role.kubernetes.io/master=""
　　
[bootstraptoken] Using token: deed3a.b3542929fcbce0f0
　　
[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 172.16.50.131:6443 --token deed3a.b3542929fcbce0f0 --discovery-token-ca-cert-hash sha256:0334022c7eb4f2b20865f1784c64b1e81ad87761b9e8ffd50ecefabca5cfad5c