kubeadm_join_phase_kubelet-start [page]deterministic

reference

Write kubelet settings, certificates and (re)start the kubelet

### Synopsis

Write a file with KubeletConfiguration and an environment file with node specific kubelet settings, and then (re)start kubelet.

``` kubeadm join phase kubelet-start [api-server-endpoint] [flags] ```

### Options

<tr> <td colspan="2">--config string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a kubeadm configuration file.</p></td> </tr>

<tr> <td colspan="2">--cri-socket string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to the CRI socket to connect. If empty kubeadm will try to auto-detect this value; use this option only if you have more than one CRI installed or if you have non-standard CRI socket.</p></td> </tr>

<tr> <td colspan="2">--discovery-file string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For file-based discovery, a file or URL from which to load cluster information.</p></td> </tr>

<tr> <td colspan="2">--discovery-token string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, the token used to validate cluster information fetched from the API server.</p></td> </tr>

<tr> <td colspan="2">--discovery-token-ca-cert-hash strings</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").</p></td> </tr>

<tr> <td colspan="2">--discovery-token-unsafe-skip-ca-verification</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.</p></td> </tr>

<tr> <td colspan="2">--dry-run</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Don't apply any changes; just output what would be done.</p></td> </tr>

<tr> <td colspan="2">-h, --help</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>help for kubelet-start</p></td> </tr>

<tr> <td colspan="2">--node-name string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Specify the node name.</p></td> </tr>

<tr> <td colspan="2">--patches string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Path to a directory that contains files named "target[suffix][+patchtype].extension". For example, "kube-apiserver0+merge.yaml" or just "etcd.json". "target" can be one of "kube-apiserver", "kube-controller-manager", "kube-scheduler", "etcd", "kubeletconfiguration", "corednsdeployment". "patchtype" can be one of "strategic", "merge" or "json" and they match the patch formats supported by kubectl. The default "patchtype" is "strategic". "extension" must be either "json" or "yaml". "suffix" is an optional string that can be used to determine which patches are applied first alpha-numerically.</p></td> </tr>

<tr> <td colspan="2">--tls-bootstrap-token string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.</p></td> </tr>

<tr> <td colspan="2">--token string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.</p></td> </tr>

</tbody> </table>

### Options inherited from parent commands

<table style="width: 100%; table-layout: fixed;"> <colgro …(trimmed)

Sources

reference/setup-tools/kubeadm/generated/kubeadm_join/kubeadm_join_phase_kubelet-start.md · doc — “kubeadm_join_phase_kubelet-start”

Related (3)

part_of Synopsis — describes conf=1

part_of Options — describes conf=1

part_of Options inherited from parent commands — describes conf=1

← all Docs