Modify kubelet node profiles

Any changes you make to a kubelet node profile will instantly affect the nodes in which the profile is in use. As such, Mirantis strongly recommends that you first test any modifications in a limited scope, by creating a new profile with the modifications and applying it to a small number of nodes.

Warning

Misconfigured modifications made to a kubelet node profile that is in use by a large number of cluster nodes can result in those nodes becoming nonoperational.

Example scenario:

You have defined the following kubelet node profiles in the MKE configuration file:

[cluster_config.custom_kubelet_flags_profiles]
  high = "--kube-reserved=cpu=200m,memory=512Mi --kube-reserved-cgroup=/high"
  low = "--kube-reserved=cpu=100m,memory=256Mi --kube-reserved-cgroup=/low"

Modify the profile definition as follows:

[cluster_config.custom_kubelet_flags_profiles]
  high = "--kube-reserved=cpu=200m,memory=512Mi --kube-reserved-cgroup=/high"
  low = "--kube-reserved=cpu=100m,memory=256Mi --kube-reserved-cgroup=/low"
  lowtest = "--kube-reserved=cpu=150m,memory=256Mi --kube-reserved-cgroup=/low"

:ref:`Apply <apply-kubelet-node-profiles>`__ the new lowtest label to a small set of test nodes.

Once the profile is verified on your test nodes, remove lowtest from the profile definition and update low to use the updated --kube-reserved=cpu value.