Unable to schedule pods on nodes it says too many pods

Shreyas Arani 266 Reputation points

Hi we have 4 node AKS cluster with 4vcpu and 16 GB RAM for each node out of which one node is tainted to run specific pods. we are getting the below message when to try deploy the pods. But when we check cpu and ram consumption of the nodes it is in acceptable range.

@SRIJIT-BOSE-MSFT can you please me to resolve the issue?

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.
1,902 questions
0 comments No comments
{count} votes

Accepted answer
  1. Manu Philip 17,006 Reputation points MVP

    Are you seeing that max pod limit reached! kubectl get nodes -o yaml | grep pods
    What is the limit? The command shows the pod count, that can be allocated to each nodes
    How many are running?
    kubectl get pods --all-namespaces | grep Running | wc -l


    1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Manu Philip 17,006 Reputation points MVP

    A taint is applied to a node that indicates only specific pods can be scheduled on them. A toleration is then applied to a pod that allows them to tolerate a node's taint. The Kubernetes scheduler can use taints and tolerations to restrict what workloads can run on nodes.
    You can find if the node has applied with taint by running the command below:

    kubectl describe node <node name> | grep Taints

    However, You can't change node taints through the CLI after the node pool is created.:
    Here is a thread discussing on this: https://github.com/Azure/AKS/issues/1402

    You may plan for a fresh new nodepool in this situation

    --please don't forget to upvote and Accept as answer if the reply is helpful--