Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1840222: Fail if no upstream DNS servers are found #63

Merged
merged 1 commit into from
May 26, 2020

Commits on May 26, 2020

  1. Fail if no upstream DNS servers are found

    Coredns will fail to start if we configure the forward plugin with
    no upstream servers. The init container responsible for rendering
    the config needs to fail if that situation arises so it can be
    retried later when hopefully resolv.conf has been populated correctly.
    
    We're not sure how it happens that there are no upstream servers,
    but it's clearly wrong for us to render an invalid config so this
    is the safe thing to do anyway.
    cybertron committed May 26, 2020
    Configuration menu
    Copy the full SHA
    6d1b195 View commit details
    Browse the repository at this point in the history