1KUBERNETES(1)(kubernetes) KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7
9 kubeadm join phase kubelet-start - Write kubelet settings, certificates
10 and (re)start the kubelet
11
12
13
15 kubeadm join phase kubelet-start [OPTIONS]
16
17
18
20 Write a file with KubeletConfiguration and an environment file with
21 node specific kubelet settings, and then (re)start kubelet.
22
23
24
26 --config="" Path to a kubeadm configuration file.
27
28
29 --cri-socket="" Path to the CRI socket to connect. If empty
30 kubeadm will try to auto-detect this value; use this option only if you
31 have more than one CRI installed or if you have non-standard CRI
32 socket.
33
34
35 --discovery-file="" For file-based discovery, a file or URL from
36 which to load cluster information.
37
38
39 --discovery-token="" For token-based discovery, the token used to
40 validate cluster information fetched from the API server.
41
42
43 --discovery-token-ca-cert-hash=[] For token-based discovery, vali‐
44 date that the root CA public key matches this hash (format: ":").
45
46
47 --discovery-token-unsafe-skip-ca-verification=false For token-
48 based discovery, allow joining without --discovery-token-ca-cert-hash
49 pinning.
50
51
52 --dry-run=false Don't apply any changes; just output what would be
53 done.
54
55
56 --node-name="" Specify the node name.
57
58
59 --patches="" Path to a directory that contains files named "tar‐
60 get[suffix][+patchtype].extension". For example, "kube-apis‐
61 erver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-
62 apiserver", "kube-controller-manager", "kube-scheduler", "etcd",
63 "kubeletconfiguration". "patchtype" can be one of "strategic", "merge"
64 or "json" and they match the patch formats supported by kubectl. The
65 default "patchtype" is "strategic". "extension" must be either "json"
66 or "yaml". "suffix" is an optional string that can be used to determine
67 which patches are applied first alpha-numerically.
68
69
70 --tls-bootstrap-token="" Specify the token used to temporarily au‐
71 thenticate with the Kubernetes Control Plane while joining the node.
72
73
74 --token="" Use this token for both discovery-token and tls-boot‐
75 strap-token when those values are not provided.
76
77
78
80 --azure-container-registry-config="" Path to the file containing
81 Azure container registry configuration information.
82
83
84 --rootfs="" [EXPERIMENTAL] The path to the 'real' host root
85 filesystem.
86
87
88 --version=false Print version information and quit
89
90
91
93 kubeadm-join-phase(1),
94
95
96
98 January 2015, Originally compiled by Eric Paris (eparis at redhat dot
99 com) based on the kubernetes source material, but hopefully they have
100 been automatically generated since!
101
102
103
104Manuals User KUBERNETES(1)(kubernetes)