Difference between revisions of "Microk8s DNS Troubleshooting"

From UVOO Tech Wiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 +
https://github.com/ubuntu/microk8s/issues/1484
 +
 +
Calico vxlan not working
 +
 +
snap remove microk8s && snap install microk8s && rejoin
 +
 +
sudo tcpdump -vvni any port 4789
 +
 +
```
 +
kubectl create deployment dnsutils --image=gcr.io/kubernetes-e2e-test-images/dnsutils:1.3 -- sleep 3600
 +
 +
  for i in {1..3}; do
 +
      echo "dnsutils$i"
 +
      kubectl -n default run dnsutils$i --image=gcr.io/kubernetes-e2e-test-images/dnsutils:1.3 -- sleep 3600
 +
      sleep 20
 +
      kubectl -n default exec -i -t dnsutils$i -- nslookup cisco.com
 +
    done
 +
```
 +
 +
 
https://github.com/ChristofSchwarz/qseok_on_Microk8s/issues/1
 
https://github.com/ChristofSchwarz/qseok_on_Microk8s/issues/1
  
Line 12: Line 32:
 
kubectl delete pod -n kube-system -l k8s-app=kube-dns
 
kubectl delete pod -n kube-system -l k8s-app=kube-dns
 
```
 
```
 +
  
 
  10.152.183.10 cluster ip address
 
  10.152.183.10 cluster ip address
 +
```
 +
$ kubectl get svc -n kube-system
 +
NAME      TYPE        CLUSTER-IP      EXTERNAL-IP  PORT(S)                  AGE
 +
kube-dns  ClusterIP  10.152.183.10  <none>        53/UDP,53/TCP,9153/TCP  77m
 +
```

Latest revision as of 02:18, 12 October 2021

https://github.com/ubuntu/microk8s/issues/1484

Calico vxlan not working

snap remove microk8s && snap install microk8s && rejoin

sudo tcpdump -vvni any port 4789

kubectl create deployment dnsutils --image=gcr.io/kubernetes-e2e-test-images/dnsutils:1.3 -- sleep 3600

   for i in {1..3}; do
      echo "dnsutils$i"
      kubectl -n default run dnsutils$i --image=gcr.io/kubernetes-e2e-test-images/dnsutils:1.3 -- sleep 3600
      sleep 20
      kubectl -n default exec -i -t dnsutils$i -- nslookup cisco.com
    done

https://github.com/ChristofSchwarz/qseok_on_Microk8s/issues/1

Get current configuration of KubeDNS (coredns)
kubectl describe configmap coredns -n kube-system

Check the logs of coredns
kubectl logs --selector k8s-app=kube-dns -n kube-system

Restart the coredns pod:
kubectl delete pod -n kube-system -l k8s-app=kube-dns

10.152.183.10 cluster ip address

$ kubectl get svc -n kube-system
NAME       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                  AGE
kube-dns   ClusterIP   10.152.183.10   <none>        53/UDP,53/TCP,9153/TCP   77m