Failed to schedule pod on AKS

Sai Theja 21 Reputation points
2023-01-23T02:40:31.05+00:00

We are facing this issue regularly,

As per Autoscale, Pods has to create and run on available nodes but

Pods are changed to pending state and taking longer time to run, meanwhile it is getting terminated.

May i know what might be the cause,

Note: Nodes are sufficiently available and kept in auto scale.

Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
2,229 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sai Theja 21 Reputation points
    2023-01-23T12:53:14.26+00:00

    Hi @srbhatta-MSFT

    Thanks for the reply,

    I have verified the logs for the problematic time stamp, it was due to node insufficiency, where as nodes are kept in autoscale mode,

    Where can i check the logs for the nodes autoscaler, what is the time period it took to allocate new node on to cluster..?

    In logs diagnostics, we have enabled

    The following logs are enabled.

    Please let me know, where we can find out the Cluster autoscaler logs.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.