Docs

Volcengine Kubernetes Engine

cluster upgrade

Will custom kubelet parameters on a node be overwritten during an upgrade?

Configuration method

VKE supports configuring kubelet parameters on nodes through different methods. Different configuration methods support different parameters, and the logic for retaining parameters during an upgrade also differs. The following table describes the details.

Configuration method	Configuration method	Post-upgrade processing logic
Use the console	Specify the kubelet parameters of the node pool in the console and allow them to be synchronized to existing nodes. For details, see Configuring Kubelet parameters for node pools. tip We recommend first using this method to configure the kubelet parameters of nodes.	The parameters are retained after the node upgrade. When synchronizing the node pool configuration to existing nodes, parameters on the existing nodes that are the same as the node pool parameters will be updated to the configuration of the node pool.
Custom configuration	For parameters that are not supported by the console, you can specify custom configurations by modifying the ConfigMap or node configuration files. For details, see Custom cluster kubelet parameters.	Parameters will not necessarily be retained after the node upgrade. During the upgrade, files such as /var/lib/kubelet/config.yaml and /var/lib/kubelet/kubeadm-flags.env may be regenerated or updated. Record the existing configuration before the upgrade and recheck whether the parameters take effect after the upgrade.

Parameter cleanup

During a node upgrade, VKE checks the compatibility of Feature Gates based on the target Kubernetes version and removes incompatible configurations. For example:

When you upgrade from v1.26 to v1.28, QoSResourceManager is removed.

IPv6DualStack is removed during the upgrade.

When you upgrade from v1.34 to v1.36, this configuration is removed from the node, including InPlacePodVerticalScaling.

warning

The actual cleanup scope is subject to the compatibility check results of the target Kubernetes version. Do not re-add Feature Gates that are not supported by the target version after the upgrade. Otherwise, it may cause kubelet startup exceptions or node unavailability.

Last updated: 2026.10.10 17:41:56