Configuration options for worker nodes#
k0s worker command does not take in any special yaml configuration, there are still methods for configuring the workers to run various components.
k0s worker command accepts the
--labels flag, with which you can make the newly joined worker node the register itself, in the Kubernetes API, with the given set of labels.
For example, running the worker with
k0s worker --token-file k0s.token --labels="k0sproject.io/foo=bar,k0sproject.io/other=xyz" results in:
$ kubectl get node --show-labels NAME STATUS ROLES AGE VERSION LABELS worker0 NotReady <none> 10s v1.20.2-k0s1 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,k0sproject.io/foo=bar,k0sproject.io/other=xyz,kubernetes.io/arch=amd64,kubernetes.io/hostname=worker0,kubernetes.io/os=linux
Note: Setting the labels is only effective on the first registration of the node. Changing the labels thereafter has no effect.
k0s worker command accepts a generic flag to pass in any set of arguments for kubelet process.
For example, running
k0s worker --token-file=k0s.token --kubelet-extra-args="--node-ip=220.127.116.11 --address=0.0.0.0" passes in the given flags to kubelet as-is. As such, you must confirm that any flags you are passing in are properly formatted and valued as k0s will not validate those flags.