This message was deleted.
# rke2
a
This message was deleted.
s
We have enabled nodelocal but in the config map it seems to point to the service IP of rke2-cored a, from reading the docs we assumed it should pick up the IP of the kube-dns service
c
nodelocal dns cache is part of the rke2-coredns chart
are you trying to deploy your own separate copy or something?
nobody actually uses kube-dns any more, coredns has been the standard replacement for ages. the service is still called that for legacy reasons.
s
Ah ok we enabled it using this https://docs.rke2.io/networking
c
that’s the normal way to enable it. I’m confused why you’re asking about disabling rke2-coredns when you just enabled a feature within it.
what are you trying to accomplish, and why would you want to disable coredns if you want to use its local cache?
s
Per this doc https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/ it says it should use the kube-dns serviceIP ? However when we check the config map for node local it is using the rke2 CoreDNS service IP
c
the “administer a cluster” section of the upstream docs are mostly meant for kubeadm clusters
s
I guess missunderstold
c
not other distros, which might package or configure things in different ways. If the RKE2 docs and upstream docs both cover something, follow the RKE2 docs.
👍 1
that page in particular appears to be specific to minikube for some reason
https://kubernetes.io/docs/tasks/administer-cluster/nodelocaldns/#introduction does cover how the implementation works, including a note about how it still uses the kube-dns/coredns address, via iptables rules.
👍 1
s
Got this all figured out and up and running now. Thanks