Hi,
It could be resources limit and request on the pod itself are higher than the exiting resources on the nodes, can you share the output of the describe command:
kubectl describe pod <pod-name> -n <namespace>
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
For one of the pod in the AKS cluster showing as pending status from long time and when I check through describe pod getting this message.
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
Also I see sufficient memory/cpu
kubectl top nodes
NAME CPU(cores) CPU% MEMORY(bytes) MEMORY%
aks-esppd1002-33124800-vmss000000 2329m 29% 23866Mi 41%
aks-esppd1002-33124800-vmss000001 3306m 42% 25075Mi 43%
aks-esppd1002-33124800-vmss000002 213m 2% 20935Mi 36%
aks-esppd1002-33124800-vmss000003 1298m 16% 27427Mi 47%
aks-esppd1002-33124800-vmss000004 1840m 23% 21765Mi 37%
aks-esppd1002-33124800-vmss000005 1157m 14% 15918Mi 27%
aks-esppd1002-33124800-vmss000006 2228m 28% 16905Mi 29%
aks-esppd1002-33124800-vmss000007 1458m 18% 17797Mi 30%
Please assist on this. Thanks
Hi,
It could be resources limit and request on the pod itself are higher than the exiting resources on the nodes, can you share the output of the describe command:
kubectl describe pod <pod-name> -n <namespace>