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 kubeadm config 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.|
|help for kubelet-start|
|Specify the node name.|
|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.|
Was this page helpful?
Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on Stack Overflow. Open an issue in the GitHub repo if you want to report a problem or suggest an improvement.