curlpod still in pending

eporart

I am checking that the curlpod still in pending status:

kubectl get pods
NAME READY STATUS RESTARTS AGE
curlpod 0/1 Pending 0 28s
hog-566989bc4f-s65x9 1/1 Terminating 0 3d23h
hog-566989bc4f-xq97q 0/1 Pending 0 2m35s

student@cp:~$ kubectl describe node curlpod | grep Taints
Error from server (NotFound): nodes "curlpod" not found
student@cp:~$ kubectl describe pod curlpod
Name: curlpod
Namespace: default
Priority: 0
Node:
Labels: name=examplepod
Annotations:
Status: Pending
IP:
IPs:
Containers:
nginx:
Image: nginx
Port: 80/TCP
Host Port: 0/TCP
Environment:
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-b7jtx (ro)
Conditions:
Type Status
PodScheduled False
Volumes:
kube-api-access-b7jtx:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors:
Tolerations: 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 11s (x16 over 16m) default-scheduler 0/2 nodes are available: 1 node(s) had taint {node.kubernetes.io/disk-pressure: }, that the pod didn't tolerate, 1 node(s) had taint {node.kubernetes.io/unreachable: }, that the pod

could you give me and advice?

thanks

chrispokorni

Hi @eporart,

I would recommend deleting all the hog deployments created in lab 4. They are consuming many of your cluster resources, crippling the control plane in the process.

Regards,
-Chris

eporart

thanks Chris... the hog deployments were deleted and now curlpod looks good