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.
DNS is crashlooping
See original GitHub issue$ microk8s.kubectl get all --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system pod/heapster-v1.5.2-84f5c8795f-m466m 4/4 Running 0 23m
kube-system pod/kube-dns-864b8bdc77-6mst4 2/3 CrashLoopBackOff 15 23m
kube-system pod/kubernetes-dashboard-6948bdb78-262gm 0/1 CrashLoopBackOff 8 23m
kube-system pod/monitoring-influxdb-grafana-v4-7ffdc569b8-dbmvg 2/2 Running 0 23m
NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
default service/kubernetes ClusterIP 10.152.183.1 <none> 443/TCP 23m
kube-system service/heapster ClusterIP 10.152.183.109 <none> 80/TCP 23m
kube-system service/kube-dns ClusterIP 10.152.183.10 <none> 53/UDP,53/TCP 23m
kube-system service/kubernetes-dashboard ClusterIP 10.152.183.178 <none> 443/TCP 23m
kube-system service/monitoring-grafana ClusterIP 10.152.183.68 <none> 80/TCP 23m
kube-system service/monitoring-influxdb ClusterIP 10.152.183.252 <none> 8083/TCP,8086/TCP 23m
NAMESPACE NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
kube-system deployment.apps/heapster-v1.5.2 1 1 1 1 23m
kube-system deployment.apps/kube-dns 1 1 1 0 23m
kube-system deployment.apps/kubernetes-dashboard 1 1 1 0 23m
kube-system deployment.apps/monitoring-influxdb-grafana-v4 1 1 1 1 23m
NAMESPACE NAME DESIRED CURRENT READY AGE
kube-system replicaset.apps/heapster-v1.5.2-84f5c8795f 1 1 1 23m
kube-system replicaset.apps/kube-dns-864b8bdc77 1 1 0 23m
kube-system replicaset.apps/kubernetes-dashboard-6948bdb78 1 1 0 23m
kube-system replicaset.apps/monitoring-influxdb-grafana-v4-7ffdc569b8 1 1 1 23m
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
DNS is crashlooping · Issue #67 · canonical/microk8s
1.0/32 subnet corresponds to the pod IP addresses: ***@***.***:~$ microk8s.kubectl get po -n kube-system -o wide NAME READY STATUS RESTARTS AGE ...
Read more >DNS CrashLoop : r/kubernetes
r/kubernetes - DNS CrashLoop. I have configured Kubernetes a few times, 3 out of 4 times I have a problem with pod/kube-dns going...
Read more >Troubleshoot DNS failures with Amazon EKS - AWS
How do I troubleshoot DNS failures with Amazon EKS? ... Verify that the DNS endpoints are exposed and pointing to CoreDNS pods:.
Read more >Kubernetes CoreDNS in CrashLoopBackOff
CoreDns pod gets crashloop backoff error. Steps followed to make the pod into running state: As Tim Chan said in this post and...
Read more >Kubernetes CrashLoopBackOff Error: What It Is and How to ...
Issue with Third-Party Services (DNS Error). Sometimes, the CrashLoopBackOff error is caused by an issue with one of the third-party services.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@tvansteenburgh OMG! I was hitting my head to wall for a week for this, works like a charm! Thanks a ton!
Inspecting the ufw log showed that all the denials were happening on the cbr0 interface.
The 10.1.1.0/32 subnet corresponds to the pod IP addresses:
So the fix was: