This message was deleted.
# rke2
a
This message was deleted.
You appear to already be setting the resources for nodelocal pods... what exactly are you asking about?
q
@creamy-pencil-82913 yes correct. Above HelmChartConfig yaml spec which i have shared is for CoreDNS, where after rke2 deploys coredns, then i apply above yaml and it works perfectly. lets say if i want to set Limit for cpu/mem resource after rancher deployes node-local then how do it set those? something like below # resources for the node-local-dns pods resources: limits: cpu: 300m memory: 512Mi requests: cpu: 25m memory: 5Mi Also, I'd like to add the following to the default NodeLocal DNS Corefile generated by RKE2:
Copy code
template ANY AAAA {
  rcode NOERROR
}
This allows NodeLocal DNS to immediately return an empty
NOERROR
response for IPv6 (AAAA) queries in our IPv4-only clusters, avoiding unnecessary upstream forwarding. Is there a supported way to customize the generated NodeLocal Corefile? below is default node-local configmap
Copy code
❯ kubectl get cm node-local-dns -n kube-system \
  -o go-template='{{index .data "Corefile"}}'
cluster.local:53 {
    errors
    cache {
            success 9984 30
            denial 9984 5
    }
    reload
    loop
    bind 169.254.20.10 100.66.0.10
    forward . __PILLAR__CLUSTER__DNS__ {
            force_tcp
    }
    prometheus :9253
    health 169.254.20.10:8080


    }
in-addr.arpa:53 {
    errors
    cache 30
    reload
    loop
    bind 169.254.20.10 100.66.0.10
    forward . __PILLAR__CLUSTER__DNS__ {
            force_tcp
    }
    prometheus :9253
    }
ip6.arpa:53 {
    errors
    cache 30
    reload
    loop
    bind 169.254.20.10 100.66.0.10
    forward . __PILLAR__CLUSTER__DNS__ {
            force_tcp
    }
    prometheus :9253
    }
.:53 {
    errors
    cache 30
    reload
    loop
    bind 169.254.20.10 100.66.0.10
    forward . __PILLAR__UPSTREAM__SERVERS__
    prometheus :9253
    }
 ~/Downloads/kube 
github.com/rancher/rke2-charts/blob/…/values.yaml#…
@creamy-pencil-82913 - do we have approach to tweak for my use-case?
i have tried few ways, however rancher reverts those and brings back to defaul spec for node-local