Managed Service for Kubernetes cluster remains in the STARTING status for too long after renaming
Written by
Updated at December 17, 2025
Issue description
- Your Managed Service for Kubernetes cluster remains in the
STARTINGstatus for too long. - In the list of operations, there are operations in the
Not completedstatus.
Solution
Renaming VMs that were automatically created as worker nodes when deploying a Managed Service for Kubernetes cluster will disrupt the operation of the node group and the entire cluster. In this article, we explicitly tell you that you should not rename such nodes.
If you still renamed your nodes, you will need to delete the problematic Managed Service for Kubernetes cluster and create a new one.