Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for Kubernetes
    • Resolving the `Timed out waiting for the condition` error when mounting a PVC
    • Resolving the `Timed out waiting for the condition` error when mounting a volume with a large number of files
    • Hosts of the Managed Service for Kubernetes node groups stay in the `RECONCILING` status for a long time
    • Cyclical restarts of the `kube-dns-autoscaler` pod
    • Cannot reduce the number of nodes in a Managed Service for Kubernetes group
    • Cannot increase the number of nodes in a Managed Service for Kubernetes group
    • Resolving the `Multi-Attach error for volume` error
    • Resolving the `DEADLINE_EXCEEDED` error
    • Troubleshooting time synchronization issues on Managed Service for Kubernetes cluster nodes
    • Troubleshooting DNS name resolving issues in Managed Service for Kubernetes
    • Resolving the `0/10 nodes are available - node(s) had untolerated taint` error
    • The cluster remains in the `STARTING` status for too long
    • Cluster pods remain in the `PENDING` status for too long
    • Troubleshooting HPA issues in Managed Service for Kubernetes
    • Resolving the `Can't use allocation_policy.locations.subnet_id together with node_template.network_interface_specs` error
    • Troubleshooting issues when mounting volumes to Managed Service for Kubernetes cluster pods using Container Storage Interface for S3
    • Managed Service for Kubernetes cluster remains `STARTING` for too long after renaming
    • How to add and update Linux SSH keys on Managed Service for Kubernetes node group hosts
    • How to assign static external IP addresses to Managed Service for Kubernetes cluster nodes
    • How to provide Kubernetes nodes with internet access
    • How to create an internal Ingress controller
    • How to set up autodeletion of old images from Managed Service for Kubernetes nodes
    • How to find out the external IP address of a Managed Service for Kubernetes node
    • How to use Certificate Manager certificates in load balancers or in Managed Service for Kubernetes
    • How to change the time zone on Managed Service for Kubernetes cluster nodes
    • How to find out the ephemeral storage size for a Managed Service for Kubernetes node

In this article:

  • Issue description
  • Diagnostics and issue reproduction
  • Solution
  1. Managed Service for Kubernetes
  2. Hosts of the Managed Service for Kubernetes node groups stay in the `RECONCILING` status for a long time

Managed Service for Kubernetes node group hosts stay in the RECONCILING status for a while

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Diagnostics and issue reproduction
  • Solution

Issue descriptionIssue description

Some (or all) VMs of your Managed Service for Kubernetes node group remain in the RECONCILING status for more than 20 minutes.

Diagnostics and issue reproductionDiagnostics and issue reproduction

  • Check your quota consumption for Managed Service for Kubernetes. If the consumption level is approaching the current quotas, request a quota increase. For this, you must have the quota-manager.requestOperator role or higher, such as editor or admin.
  • If the quotas are not exceeded, check the state of VMs belonging to the node group through this command:
yc managed-kubernetes node-group list-nodes <node_group_id> --format yaml

If the command output includes the Kubelet stopped posting node status message, it means the VM belonging to the node group experienced a failure in the OS or application services that ensure operability of this host within the node group.

SolutionSolution

Follow these steps to fix the issue:

  1. Connect to the VM in question over SSH. You can learn how to do it in this Managed Service for Kubernetes guide.
  2. Establish an interactive session with the problematic VM and run the following commands:
    sudo service containerd restart
    sudo service kubelet restart
    

Note

To check the service status, use the following commands:

service containerd status
service kubelet status

Make sure the services are ACTIVE and their logs are error-free.

Alternatively, you can restart your VM from the management console or YC CLI.

Was the article helpful?

Previous
Resolving the `Timed out waiting for the condition` error when mounting a volume with a large number of files
Next
Cyclical restarts of the `kube-dns-autoscaler` pod
© 2026 Direct Cursus Technology L.L.C.