question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pods stuck in pending after install

See original GitHub issue

Hello,

After installing microk8s from snap in Ubuntu 18.04.1 LTS (VirtualBox VM under Win10 Home) I’ve got pods in pending state.

dev@kube1:~$ sudo microk8s.kubectl get pods --all-namespaces
NAMESPACE     NAME                                              READY   STATUS    RESTARTS   AGE
kube-system   heapster-v1.5.2-6bc7c4965d-sdkcz                  0/4     Pending   0          108m
kube-system   kube-dns-6ccd496668-79d6g                         0/3     Pending   0          108m
kube-system   kubernetes-dashboard-654cfb4879-dh6gb             0/1     Pending   0          108m
kube-system   monitoring-influxdb-grafana-v4-6679c46745-md7tx   0/2     Pending   0          108m
dev@kube1:~$

Don’t know what else to do or how to tshoot specific pods. I can’t seem to find the logs… inspection-report-20190304_152125.tar.gz Inspect attached. One of the cases mentions DNS problem on the host but I’ve checked it and it’s ok:. Here are the iptables rules in case it matters. iptables.rules.txt

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:11 (2 by maintainers)

github_iconTop GitHub Comments

3reactions
chradcliffecommented, Feb 12, 2020

In case anyone is following the same breadcrumb trail, the new issue created by @shukalo83 was #347

1reaction
tdensmorecommented, May 29, 2019

I am trying to follow the thread that was started with https://github.com/ubuntu/microk8s/issues/184

Can you please post the link to the new Issue that was created for this? @shukalo83

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshooting Kubernetes Pods: Stuck in a "Pending" State
There are two common reasons for a pod to fail to be scheduled to a node. First, it may be bound to hostPort....
Read more >
Why do Kubernetes pod stay in pending state? - Stackify
What happens if your Kubernetes pod stays in pending state? This cannot be programmed into a node as inadequate resources prevent proper ...
Read more >
Pod Stuck in Pending State – Runbooks - GitHub Pages
Detailed Steps · 1) Gather information · 2) Examine pod Events output. · 3) Check the kubelet logs · 4) Is this a...
Read more >
How to Debug Kubernetes Pending Pods and Scheduling ...
Learn how to debug Pending pods that fail to get scheduled due to resource constraints, taints, affinity rules, and other reasons.
Read more >
Debug Pods - Kubernetes
If a Pod is stuck in Pending it means that it can not be scheduled onto a node. Generally this is because there...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found