Pods stuck in pending with Insufficient memory while workers have free memory

Solution Verified - Updated -

Issue

  • Pods are stuck in Pending state due to insufficient memory; An example of this error is provided below:

    0/6 nodes are available: 3 Insufficient memory, 3 node(s) had taint {node-role.kubernetes.io/master: }, that the pod didn't tolerate.
    

    When reviewing the Worker Nodes, it appears they have lots of available memory.

    $ oc adm top node
    NAME           CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
    worker1        2231m        11%    19831Mi         53%
    worker2        3459m        17%    32418Mi         87%
    worker3        6492m        33%    23469Mi         63%
    

    The Pod is requesting less than the available above, why is the Pod not be scheduled?

      - resources:
          limits:
            cpu: 500m
            memory: 500Mi
          requests:
            cpu: 500m
            memory: 500Mi
    
  • Why are the oc adm top nodes and the oc describe nodes/<node-name> available resource values different?

Environment

  • OpenShift Container Platform
    • 4.X

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content