Why do I see a failed to set feature gates
error when upgrading a worker node?
When you try to upgrade a worker node in a cluster with a Cloud Pak installation, the worker node goes from Ready
to Critical
and stays in Critical
. Check if a ConfigMap exists for the Cloud Pak deployer
by running kubectl get cm cloud-pak-node-fix-config -n kube-system -o yaml
.
This error happens because the Cloud Pak deployer (cloud-pak-deployer
) makes changes to the kubelet config file. However, if the kubelet config file contains changes between versions, for example between 4.10 and 4.11, then the deployer
doesn't update the config file.
If you see this error, you must manually update the cloud-pak-node-fix-config
configmap.
Review the following steps based on your target cluster version.
Upgrading from 4.11 to 4.12
-
Edit the ConfigMap and remove the following feature gates.
CSIMigrationAWS: False CSIMigrationGCE: False CRIContainerLogRotation: true
kubectl edit cm cloud-pak-node-fix-config -n kube-system -o yaml
-
Reboot the worker node.
-
After rebooting, continue to upgrade your worker nodes.
-
If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.
Upgrading from 4.10 to 4.11
-
Edit the ConfigMap and remove the following feature gates.
CSIMigrationOpenStack ServiceLBNodePortControl CSIMigrationAzureDisk
kubectl edit cm cloud-pak-node-fix-config -n kube-system -o yaml
-
Reboot the worker node.
-
After rebooting, continue to upgrade your worker nodes.
-
If the issue persists, contact support. Open a support case. In the case details, be sure to include any relevant log files, error messages, or command outputs.