pod status pending from long time

Question

pod status pending from long time

37821879 90

Hi Team, For one of the pod in AKS I am getting the below error though I have sufficient memory and cpu

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  33m (x19 over 124m)  default-scheduler  0/8 nodes are available: 3 Insufficient cpu, 8 Insufficient memory. preemption: 0/8 nodes are available: 8 No preemption victims found for incoming pod.

37821879 90

kubectl describe pod espcctpurecloudtool-79d594948b-j4snj -n esp-prod
Name:             espcctpurecloudtool-79d594948b-j4snj
Namespace:        esp-prod
Priority:         0
Service Account:  default
Node:             <none>
Labels:           app=espcctpurecloudtool
                  pod-template-hash=79d594948b
Annotations:      <none>
Status:           Pending
IP:
IPs:              <none>
Controlled By:    ReplicaSet/espcctpurecloudtool-79d594948b
Containers:
  espcctpurecloudtool:
    Image:      acrinfpd1001.azurecr.io/espcctpurecloudtool:421099
    Port:       8080/TCP
    Host Port:  0/TCP
    Limits:
      cpu:     4500m
      memory:  1Ti
    Requests:
      cpu:     3
      memory:  1Ti
    Environment Variables from:
      espcctpurecloudtool-config  ConfigMap  Optional: false
    Environment:
      TZ:  America/New_York
    Mounts:
      /etc/localtime from timezone-config (rw)
      /mnt/azure from azure (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mn9gh (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  timezone-config:
    Type:          HostPath (bare host directory volume)
    Path:          /usr/share/zoneinfo/America/New_York
    HostPathType:  File
  azure:
    Type:        AzureFile (an Azure File Service mount on the host and bind mount to the pod)
    SecretName:  esp-prod-logs-secret
    ShareName:   application-prod-logs
    ReadOnly:    false
  kube-api-access-mn9gh:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Warning  FailedScheduling  33m (x19 over 124m)  default-scheduler  0/8 nodes are available: 3 Insufficient cpu, 8 Insufficient memory. preemption: 0/8 nodes are available: 8 No preemption victims found for incoming pod.

Accepted answer

0 additional answers

Your answer

37821879 90 Reputation points

2023-08-08T10:23:37.3566667+00:00

kubectl describe pod espcctpurecloudtool-79d594948b-j4snj -n esp-prod Name: espcctpurecloudtool-79d594948b-j4snj Namespace: esp-prod Priority: 0 Service Account: default Node: <none> Labels: app=espcctpurecloudtool pod-template-hash=79d594948b Annotations: <none> Status: Pending IP: IPs: <none> Controlled By: ReplicaSet/espcctpurecloudtool-79d594948b Containers: espcctpurecloudtool: Image: acrinfpd1001.azurecr.io/espcctpurecloudtool:421099 Port: 8080/TCP Host Port: 0/TCP Limits: cpu: 4500m memory: 1Ti Requests: cpu: 3 memory: 1Ti Environment Variables from: espcctpurecloudtool-config ConfigMap Optional: false Environment: TZ: America/New_York Mounts: /etc/localtime from timezone-config (rw) /mnt/azure from azure (rw) /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-mn9gh (ro) Conditions: Type Status PodScheduled False Volumes: timezone-config: Type: HostPath (bare host directory volume) Path: /usr/share/zoneinfo/America/New_York HostPathType: File azure: Type: AzureFile (an Azure File Service mount on the host and bind mount to the pod) SecretName: esp-prod-logs-secret ShareName: application-prod-logs ReadOnly: false kube-api-access-mn9gh: Type: Projected (a volume that contains injected data from multiple sources) TokenExpirationSeconds: 3607 ConfigMapName: kube-root-ca.crt ConfigMapOptional: <nil> DownwardAPI: true QoS Class: Burstable Node-Selectors: <none> Tolerations: node.kubernetes.io/memory-pressure:NoSchedule op=Exists node.kubernetes.io/not-ready:NoExecute op=Exists for 300s node.kubernetes.io/unreachable:NoExecute op=Exists for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 33m (x19 over 124m) default-scheduler 0/8 nodes are available: 3 Insufficient cpu, 8 Insufficient memory. preemption: 0/8 nodes are available: 8 No preemption victims found for incoming pod.

Answer 1

Mutaz Nassar 2,361 Microsoft Employee

Hi,

You posted the same question twice, https://learn.microsoft.com/en-us/answers/questions/1342879/pod-showing-pending-state

From the describe pod output it seems you added high request and limit:

  Limits:
      cpu:     4500m
      memory:  1Ti
    Requests:
      cpu:     3
      memory:  1Ti

Can you reduce these values based on your nodes resources

Share via

pod status pending from long time

0 additional answers

Your answer