Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for Managed Service for Kubernetes
    • Fixing 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
    • Constant restarts of the kube-dns-autoscaler pod
    • Number of nodes in the group fails to decrease
    • Resolving the "Multi-Attach error for volume" error
    • Resolving the "DEADLINE_EXCEEDED" error
    • Adding and updating Linux SSH keys on Managed Services for Kubernetes node group hosts
    • Assigning static external IP addresses for Managed Service for Kubernetes cluster nodes
    • Granting internet access to Kubernetes nodes
    • How to change the network or subnet for an MDB cluster
    • How to create an internal Ingress controller

In this article:

  • Issue description
  • Troubleshooting and reproducing issues
  • Solution
  1. Managed Kubernetes
  2. Hosts of the Managed Service for Kubernetes node groups stay in the Reconciling status for a long time

Hosts of the Managed Service for Kubernetes node groups stay in the Reconciling status for a long time

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Troubleshooting and reproducing issues
  • Solution

Issue descriptionIssue description

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

Troubleshooting and reproducing issuesTroubleshooting and reproducing issues

  • Check your quota consumption on Managed Service for Kubernetes. If the consumption level is approaching the current quotas, request quota increase. You must have the quota-manager.requestOperator role or higher (editor or admin).
  • The quotas are not exceeded, check the state of VM instances belonging to the node group by the 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 that the instance 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

  1. Use SSH to connect to the problem instance.
    To learn how to connect to another node over SSH, see the documentation.

  2. Establish an interactive session with the problem instance and execute 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 in the Active status and their logs are error-free.

Alternatively, you can restart your instance 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
Constant restarts of the kube-dns-autoscaler pod
© 2025 Direct Cursus Technology L.L.C.