The cluster remains in the STARTING status for too long

Issue descriptionIssue description

• When trying to create or run an existing Managed Service for Kubernetes cluster, its status switches to STARTING but even after a while does not switch to RUNNING.
• The cluster is stuck in the STARTING status.
• The Managed Service for Kubernetes cluster state does not switch to RUNNING.

SolutionSolution

A Managed Service for Kubernetes cluster may get stuck while being created or started because one or multiple quotas listed below have been exceeded:

• Number of vCPUs for instances
• Total VM RAM
• Number of disks
• Total HDD capacity
• Total SSD capacity
• Number of Kubernetes clusters
• Number of node groups
• Number of nodes
• Total number of vCPUs for all nodes
• Total amount of RAM
• Total disk capacity

Follow these steps to solve the issue:

1. Check your consumption by the quotas listed above. If your consumption exceeds one or multiple quotas or it is close to exceeding, resource creation operations may end in error. You can check the current quota usage and request the quota increase on this page.

2. Check whether a service account is attached to your Managed Service for Kubernetes cluster, and it has all required roles:

   • k8s.clusters.agent is required for all service accounts attached to any Managed Service for Kubernetes clusters.
   • vpc.publicAdmin is required for the service accounts attached to Managed Service for Kubernetes clusters that have their master nodes or worker nodes mapped to public IP addresses.

If the issue persistsIf the issue persists

If the above actions did not help, create a support ticket. When creating a ticket, specify the Managed Service for Kubernetes cluster ID in question.