Implement Node Local DNS operator

[stealthybox]

@justinsb is working on a self-contained using the previoulsy vetted CoreDNS DaemonSet.

The node intercept and eviction-fallback mechanisms are not completely general, but the immediate goal is to ship variants of the addon that are useful for cluster-owners on AWS where DNS latency can be very problematic. Similar issues are faced at scale in other environments. (TODO: link other issues)

Creating an operator for managing this and packaging it with kustomize for shipping the different variants should allow this to compose with the addon-installer library for clients like kops and kubeadm (kubernetes/kubeadm#1220).

/assign @justinsb
/kind feature
/sig cluster-lifecycle
/sig network

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[neolit123]

/lifecycle frozen

[dhawal55]

Any update on this? Is there any workaround to run NodeLocal DNSCache on kubeadm managed clusters?

[praseodym]

@dhawal55 you can follow the instructions at https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/#configuration

[dhawal55]

@praseodym Do you know if kubeadm supports this?

[praseodym]

@dhawal55 Those instructions work for clusters deployed with kubeadm. Kubeadm doesn’t yet support deploying NodeLocal DNSCache by itself: that is what this issue is about.