Added new node to my kubernetes cluster, why is it still in provisioning state after an hour?

Posted December 22, 2020 645 views
KubernetesDigitalOcean Managed Kubernetes

Hi community,
I followed the tutorial here, and tried to add a new (second) node to my existing node pool:

After an hour, it is still “provisioning”. I cannot access the kubernetes dashboard, neither can I deploy anything with kubectl (I get the error “Unable to connect to the server: dial tcp … i/o timeout”

I also get a “Sorry, something went wrong” message in the UI.

Does anybody have an idea?

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer

Hey @rpalyafari,

So sorry to hear you’re experiencing this. This can occur if you have any API heavy workloads deployed that put a strain on the master node. If you want you can open a support ticket. I can dig in to see what’s occurring on your cluster’s control plane.

Best Regards,
Purnima Kumari
Developer Support Engineer II - DigitalOcean