config coredns refreshes without saving my changes

0
votes

I am editing the coredns configuration so that it can resolve the test-db and test-st dns.

.:53 {
    errors
    health
    kubernetes cluster.local in-addr.arpa ip6.arpa {
      pods insecure
      fallthrough in-addr.arpa ip6.arpa
    }
    prometheus :9153
    forward . /etc/resolv.conf
    cache 30
    loop
    reload
    loadbalance
}
test-db.com:53 {
    errors
    cache 30
    forward . 10.1.5.91
}
test-st.local:53 {
    errors
    cache 30
    forward . 10.1.31.95
}

after adding the changes it works correctly for a short time (approximately 5 minutes) after that the coredns config is reloaded and my changes disappear, remaining as follows;

.:53 {
    errors
    health
    kubernetes cluster.local in-addr.arpa ip6.arpa {
      pods insecure
      fallthrough in-addr.arpa ip6.arpa
    }
    prometheus :9153
    forward . /etc/resolv.conf
    cache 30
    loop
    reload
    loadbalance
}

I have tried to apply the changes in the coredns config and then remove the core pods but it still performs the same action.

Log Pod Core

technical details

k8s version: 1.22 (eks) coredns version: v1.8.7-eksbuild.1

I appreciate your help.

kubernetesamazon-ekscoredns