Related

Product Managed Kubernetes on DigitalOcean Product
Kubernetes cluster outages Question Question
Kubernetes: How do I access the CA to sign a new user certificate? Question Question

Question

Kubernetes coredns not working for external address

Posted July 26, 2019 2.5k views
DigitalOceanKubernetes

Im using Digital Ocean kubernetes. My pod stops resolving external address. for the kubernetes names, everything is ok.

If I reboot the kubernetes nodes, its works, bbut for a short period of time.

Add a comment
vitorlavor
By:
vitorlavor
Add a comment
2 comments
  • jkwiatkoski July 26, 2019
    Reply Report

    Hi there!

    Do you see any logs in the coredns pods or any restarts on the coredns pods themselves?

    Regards,

    John Kwiatkoski
    Senior Developer Support Engineer

  • vitorlavor July 26, 2019
    Reply Report

    Nope. Coredns logs are ok:
    2019-07-26T19:53:18.670Z [INFO] CoreDNS-1.3.1
    2019-07-26T19:53:18.670Z [INFO] linux/amd64, go1.11.4, 6b56a9c
    CoreDNS-1.3.1
    linux/amd64, go1.11.4, 6b56a9c
    2019-07-26T19:53:18.670Z [INFO] plugin/reload: Running configuration MD5 =

    and 0 restarts.

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers
MilesWeb July 30, 2019

Not sure of the information about your upgrade, the issue seems to be due to kube-dns version resolving external name services. You have to roll back kube-dns to a previous build or upgrade to.

OR try to check if your kube-dns version changed whenever you upgraded your OS.

Reply Report
a7i October 4, 2019

I am running into the same issue on DOKS. What version did you upgrade/downgrade to?

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help