Modifying CoreDNS and local-node-dns is overwritten when using Claudie #1377
Replies: 3 comments 2 replies
-
Can you give us some more feedback as to which changes you have made ? I wasn't able to reproduce this on my side. I tried the following edit the configmap via
append
at the end of the Corefile for CoreDNS. Then I tried to remove/add nodes in the Claudie YAML triggering the Claudie workflow and the changes in the config map persisted |
Beta Was this translation helpful? Give feedback.
-
Thanks @Despire
But even messing with autoscale max/min numbers e.g
I might not need to touch this stuff, but without changing this stuff, CoreDNS is completely bypassed. This might be just me trying to create workarounds that should not be happening? But then again - this local-node-dns mean there are multiple DNS configs, and CoreDNS on its own cannot really do much. Thanks |
Beta Was this translation helpful? Give feedback.
-
I see, you are right the node-local-dns configmap is overwritten. After some internal discussion, what we can do is to disable deploying Do you think that this would work for you ? |
Beta Was this translation helpful? Give feedback.
-
Hey and thanks for the great work!
I am modifing CoreDNS + local DNS in my Claudie cluster configmaps as explained in here https://kubernetes.io/docs/tasks/administer-cluster/dns-custom-nameservers/ .
The problem I have is everytime I modify Claudie YAMLs, this config is being overwritten and reverted back to default, breaking my cluster as all the custom DNS records are deleted.
Is there a way to workaround this behavior?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions