Write kubelet settings, certificates and (re)start the kubelet
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]
Path to a kubeadm configuration file.
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.
For file-based discovery, a file or URL from which to load cluster information.
For token-based discovery, the token used to validate cluster information fetched from the API server.
For token-based discovery, validate that the root CA public key matches this hash (format: "<type>:<value>").
For token-based discovery, allow joining without --discovery-token-ca-cert-hash pinning.
Don't apply any changes; just output what would be done.
help for kubelet-start
Specify the node name.
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". "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.
Specify the token used to temporarily authenticate with the Kubernetes Control Plane while joining the node.
Use this token for both discovery-token and tls-bootstrap-token when those values are not provided.
Options inherited from parent commands
[EXPERIMENTAL] The path to the 'real' host root filesystem.