After scaling up a nodepool for AKS the node is not showing

Sebastian Näfe 6

Hi,

I tried to scale a nodepool. When scaling down it works just fine, but when scaling up the additional nodes are not visible via kubectl get nodes. I tried both using the Azure UI and the Azure cli. Any help appreciated.

Regards,
Sebastian

vipullag-MSFT 26,021 Reputation points

2021-05-07T06:30:46.47+00:00
@Sebastian Näfe
The issue is that kubelet cannot be joined to the master.
Below are few pointers that you can check and see if that helps to find the issue:

Is the node VM (or VMSS) Succeeded and Running? If not then you may have to troubleshoot the Linux VM (or VMSS).

Else SSH into the node and check if kubelet service and docker service are running using sudo systemctl status kubelet and sudo systemctl status docker respectively.
If they are not running start them using sudo systemctl start <serviceName>

Is scale up giving a success response or is it failing. It can be that required endpoints are blocked. Please allow the endpoints mentioned here and AgentPoolExtensionProvisioning errors might be there.

If using custom DNS maybe the node cannot resolve to the required endpoints. [Leads to similar errors as above]

Share via

After scaling up a nodepool for AKS the node is not showing