Use the following guidelines and suggested steps to help resolve kubelet service issues that occur after upgrading UCP Advisor.
- Condition:
- The kubelet service become unavailable if the Master Node VM is rebooted after upgrading UCP Advisor to version 4.4.
- What it Means:
- Running any kubectl command causes the following error:
The connection to the server xx.xx.xx.xx:6443 was refused - did you specify the right host or port?
- Corrective Action:
- Using SSH, log on to the Master Node VM.
- Navigate to the /var/lib/kubelet folder.
- In Edit mode, open the config.yaml file.
- Update the value for the cgroupDriver parameter to systemd.
- Exit Edit mode: press the Esc key.
- Save the changes. Enter:
:wq
- Run the following commands to restart the kubelet service:
systemctl stop kubelet systemctl stop docker iptables --flush iptables -tnat --flush systemctl start docker systemctl start kubelet