Hi hfpiao,

A pending state means that Kubernetes is unable to schedule a pod for execution due to insufficient resources (CPU and memory). Please perform a “describe” on those pods and check the listed events in the output. Further, please “describe” the node to check the CPU and memory pressure.

Commands:

  kubectl describe pod <pod name> -n <ifs namespace>
  kubectl describe node

Best regards, Ben

Hi Ben

Thank you very much.

According to what you said, the CPU has been increased, and most of it can run, but there are still some parts that are not in execution status, and there is no relevant information about the Event.

Please refer to the attachment.

Hi hfpio,

• ifsapp-reporting

The "describe" indicates:

0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod.

Can you please share the output for "kubectl describe node"?

• ifsapp-odata:

The output has...
  Status:       Failed
  Reason:       Evicted
  Message:      Pod ephemeral local storage usage exceeds the total limit of containers 1G. 
  ...
  Reason: ContainerStatusUnknown
  Message: The container could not be located when the pod was terminated.

Please check the logs (for each container):

kubectl logs <ifsapp-odata> -c ifsapp-odata -n <namespace>
kubectl logs <ifsapp-odata> -c linkerd-proxy -n <namespace>

You can also try deleting the pod. It will be re-created.

kubectl delete pod <ifsapp-odata> -n <namespace>

• ifs-db-init:

This is one-time task. Completed is what you want to see.

Best regards, Ben

Hi Ben

Thank you. solved.