This message was deleted.
# k3sa
adamant-kite-43734
11/20/2023, 9:04 AMThis message was deleted.
👀 1
b
brave-afternoon-4801
11/20/2023, 1:05 PMCan you explain what happened first? Was there a series of steps that arrived at the ConfigMap no longer working?
m
millions-lock-94892
11/20/2023, 1:14 PMwe had an upgrade of the underline servers, and I guess k3s service has been restarted and went back to it's default conf of coredns
millions-lock-94892
11/20/2023, 1:16 PMWhen I checked the coredns configmap, I couldn't see anymore the nameserver I added before the upgrade
b
brave-afternoon-4801
11/20/2023, 1:41 PMUm, this is an interesting problem. k3s ships with coredns manifests instead of a helmchart. That means that if you don't prep the OS with your own
/var/lib/rancher/k3s/server/manifests/coredns.yaml👍 1
brave-afternoon-4801
11/20/2023, 1:41 PMit might even happen with a k3s restart
brave-afternoon-4801
11/20/2023, 1:41 PMand this goes for every node
brave-afternoon-4801
11/20/2023, 1:43 PMYou could maybe make this easier on people in the future by appealing to k3s to embed the chart like it does for traefik and somehow using that, which would have more predictable behavior with no conflicting
HelmChartConfigbrave-afternoon-4801
11/20/2023, 1:46 PMThe short term solution is to either:
• modify that file before k3s starts
• delete the entire directory (i haven't verified this, but i think it should work fine)
m
millions-lock-94892
11/20/2023, 2:18 PMHow about deploying a custom configmap for coredns and have coredns merge it to the main conf shiped by k3s ? I rmemeber that I came across this feature one day but I don't remeber how it can be configured
b
brave-afternoon-4801
11/20/2023, 2:19 PMyeah i haven't heard about any such function. sounds interesting. if you figure it out, let me know 🙂
m
millions-lock-94892
11/20/2023, 2:19 PMsure will do
39 Views