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.

Sign up for GitHub

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

Jump to bottom

DNS is not highly-available #6

Open
justinas opened this issue Feb 13, 2022 · 1 comment
Open

DNS is not highly-available #6

justinas opened this issue Feb 13, 2022 · 1 comment

Comments

@justinas
Copy link
Owner

Currently, we run one CoreDNS service per worker node (good), but the containers' resolv.conf points only to the host node itself as the name server (bad):

nixos-ha-kubernetes/modules/worker/coredns.nix

Line 39 in f9d01ef

services.kubernetes.kubelet.clusterDns = nodeIP self;

If Kubelet is alive, but CoreDNS is dead on the node, containers running on that node will fail to resolve names.
@hughjfchen
Copy link

Looks like no easy way to fix this because services.kubernetes.kubelet.clusterDns only accepts string

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@justinas @hughjfchen