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

Implement Node Local DNS operator #34

Open
stealthybox opened this issue Nov 13, 2019 · 10 comments
Open

Implement Node Local DNS operator #34

stealthybox opened this issue Nov 13, 2019 · 10 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@stealthybox
Copy link
Contributor

@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

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network. labels Nov 13, 2019
@fejta-bot
Copy link

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 16, 2020
@neolit123
Copy link
Member

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 16, 2020
@dhawal55
Copy link

dhawal55 commented Jun 2, 2020

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

@praseodym
Copy link

@dhawal55
Copy link

dhawal55 commented Jun 3, 2020

@praseodym Do you know if kubeadm supports this?

@praseodym
Copy link

@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.

@dhawal55
Copy link

dhawal55 commented Jun 4, 2020

@praseodym If I understand this correctly, in order for client pods to use local DNSCache, the clusterDNS flag for kubelet needs to be updated to point to the local ip first.

Can you help me understand what causes client pods to use local ip for DNS?

@praseodym
Copy link

@dhawal55 According to the docs, that’s only if using kube-proxy in IPVS mode. Also, if you have further questions about using this feature https://discuss.kubernetes.io/ is probably a better place to ask those.

@dhawal55
Copy link

dhawal55 commented Jun 4, 2020

@praseodym Ah, I missed the part where it says it's only needed for kube-proxy in IPVS mode. Thank you for your help.

@somtochiama
Copy link
Member

Hello @dhawal55. I am working on this issue as part of the Google Summer of Code 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Development

No branches or pull requests

8 participants