NAME¶

kubeadm join phase kubelet-start - Write kubelet settings, certificates and (re)start the kubelet

SYNOPSIS¶

kubeadm join phase kubelet-start [OPTIONS]

DESCRIPTION¶

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

OPTIONS¶

--config="" Path to kubeadm config file.

--cri-socket="" 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.

--discovery-file="" For file-based discovery, a file or URL from which to load cluster information.

--discovery-token="" For token-based discovery, the token used to validate cluster information fetched from the API server.

--discovery-token-ca-cert-hash=[] For token-based discovery, validate that the root CA public key matches this hash (format: ":").

--discovery-token-unsafe-skip-ca-verification=false For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.

--node-name="" Specify the node name.

--tls-bootstrap-token="" Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.

--token="" Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.

OPTIONS INHERITED FROM PARENT COMMANDS¶

--azure-container-registry-config="" Path to the file containing Azure container registry configuration information.

--rootfs="" [EXPERIMENTAL] The path to the 'real' host root filesystem.

--version=false Print version information and quit

SEE ALSO¶

kubeadm-join-phase(1),

HISTORY¶

January 2015, Originally compiled by Eric Paris (eparis at redhat dot com) based on the kubernetes source material, but hopefully they have been automatically generated since!