If a Pod is stuck in Pending it means that it can not be scheduled onto a node. Generally this is because there are insufficient resources of one type or another that prevent scheduling. Look at the output of the kubectl describe ... command above. There should be messages from the scheduler about why it can not schedule your pod. Reasons include:
You don’t have enough resources: You may have exhausted the supply of CPU or Memory in your cluster, in this case you need to delete Pods, adjust resource requests, or add new nodes to your cluster. See Compute Resources document for more information.
You are using hostPort: When you bind a Pod to a hostPort there are a limited number of places that pod can be scheduled. In most cases, hostPort is unnecessary, try using a Service object to expose your Pod. If you do require hostPort then you can only schedule as many Pods as there are nodes in your Kubernetes cluster.
Have a look at the Kubernetes cluster troubleshoot guide: https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application/
This issue strikes when the pod is unable to connect to the master server. This is very common when you set up an EKS cluster. These are two things you need to keep in mind for the cluster to be fine.
You get this error when your pod ...READ MORE
root@kmaster:/home/master# kubectl get pods -o wide --all-namespaces
NAMESPACE ...READ MORE
I'm not sure but you can try ...READ MORE
Make sure that your pod yaml file ...READ MORE
Hey @nmentityvibes, you seem to be using ...READ MORE
Try using ingress itself in this manner
except ...READ MORE
Hi Kalgi after following above steps it ...READ MORE
Follow these steps:
$ kubeadm reset
$ kubeadm init ...READ MORE
If a Pod is stuck in the Waiting state, ...READ MORE
Hey @Shyam, you get this error because ...READ MORE