"Kubeadm join"의 두 판 사이의 차이

2024년 2월 25일 (일) 02:39 판

1 개요

kubeadm join

2 예시 1

master

root@master1:~# kubeadm token list
TOKEN                     TTL       EXPIRES                     USAGES                   DESCRIPTION                                                EXTRA GROUPS
i50r58.e8dx9hd9m6tmv6603  23h       2019-05-28T16:17:39+09:00   authentication,signing   The default bootstrap token generated by 'kubeadm init'.   system:bootstrappers:kubeadm:default-node-token

root@master1:~# openssl x509 -pubkey -in /etc/kubernetes/pki/ca.crt | openssl rsa -pubin -outform der 2>/dev/null | openssl dgst -sha256 -hex
(stdin)= e8ee89003791b7340e6361b8f20663571d1156d393057fc8a816857b0f965984

worker

root@worker02:~# kubeadm join --token i50r58.e8dx9hd9m6tmv6603 172.20.0.150:6443 --discovery-token-ca-cert-hash sha256:e8ee89003791b7340e6361b8f20663571d1156d393057fc8a816857b0f965984
[preflight] Running pre-flight checks
	[WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
...
This node has joined the cluster:
* Certificate signing request was sent to apiserver and a response was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the control-plane to see this node join the cluster.

3 예시 2

master

master1:~$ kubeadm token list
TOKEN                     TTL       EXPIRES                USAGES            DESCRIPTION                                                EXTRA GROUPS
102952.1a7dd4cc8d1f4cc5   23h       2019-03-24T13:22:58Z   authentication,signing   The default bootstrap token generated by 'kubeadm init'.   system:bootstrappers:kubeadm:default-node-token

worker

worker02:~$ kubeadm join --discovery-token-unsafe-skip-ca-verification --token=102952.1a7dd4cc8d1f4cc5 172.17.0.21:6443
[preflight] running pre-flight checks
        [WARNING RequiredIPVSKernelModulesAvailable]: the IPVS proxier will not be used, because the following required kernel modules are not loaded: [ip_vs ip_vs_rr ip_vs_wrr ip_vs_sh] or no builtin kernel ipvs support: map[ip_vs:{} ip_vs_rr:{} ip_vs_wrr:{} ip_vs_sh:{} nf_conntrack_ipv4:{}]
you can solve this problem with following methods:
 1. Run 'modprobe -- ' to load missing kernel modules;
2. Provide the missing builtin kernel ipvs support
...
This node has joined the cluster:
* Certificate signing request was sent to master and a response
  was received.
* The Kubelet was informed of the new secure connection details.

Run 'kubectl get nodes' on the master to see this node join the cluster.

4 같이 보기

@@ 59번째 줄: / 59번째 줄: @@
 * [[kubeadm token create]]
 * [[kubectl get nodes]]
+* [[The cluster-info ConfigMap does not yet contain a JWS signature for token ID]]
 [[분류: kubeadm]]