0% found this document useful (0 votes)
24 views

What Happened Core DNS Not Ready

Uploaded by

Rohan Ashish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
24 views

What Happened Core DNS Not Ready

Uploaded by

Rohan Ashish
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

What happened:

Coredns in k8s is running but not ready.

# kubectl get po
NAME READY STATUS RESTARTS AGE
coredns-746fcb4bc5-6qhtl 0/1 Running 0 40m
The log of coredns:

# kubectl logs coredns-746fcb4bc5-6qhtl


[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
.:53
cluster.local.:53
[INFO] plugin/reload: Running configuration MD5 = 528a67c20a203cc830e48e3dbcd28c8d
CoreDNS-1.8.4
linux/amd64, go1.16.4, 053c4d5
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
[INFO] plugin/ready: Still waiting on: "kubernetes"
The services of k8s:

# kubectl get svc


NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
AGE
kube-dns ClusterIP 20.1.0.100 <none> 53/UDP,53/TCP,9153/TCP
48m
kubernetes ClusterIP 20.1.0.1 <none> 443/TCP
124m
The configmap of coredns:

# kubectl describe cm coredns


Name: coredns
Namespace: default
Labels: <none>
Annotations: <none>

Data
====
Corefile:
----
cluster.local {
errors
health
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
}
prometheus :9153
ready :8181
forward . /etc/resolv.conf
cache 30
loop
reload
loadbalance
}
. {
cache 30
loadbalance
forward . /etc/resolv.conf
}
The parameters of kubelet:
/usr/bin/kubelet --kubeconfig=/etc/kubernetes/kubeconfig-ssl --hostname-override=k8s-node-12 --
log-dir=/var/log/kubernetes --cluster-dns=20.1.0.100 --cluster-domain=cluster.local --v=0

You might also like