For configuring a multicluster Isito with replicated control planes, one of the requirements is to configure the k8s coredns service in the kube-system namespace, to forward zone "global" to the IP of the "istiocoredns" service deployed in the istio-system namespace. Like this:
global:53 {
errors
cache 30
forward . $(kubectl get svc -n istio-system istiocoredns -o jsonpath={.spec.clusterIP}):53
}
In the example the use that command expansion to get the IP of the istiocoredns ClusterIP type of service.
As that is a non static IP and could be modified, I am looking for a way to use something more dynamic and change aware. Using the istiocoredns service FQDN name would be great, but coredns documentation is not mentioning anything about it.
Is there any coredns plugin or workaround this?
Thank you.
There is istio coredns plugin, but as mentioned in the usage section they set here the IP of the coredns anyway.
But here's some interesting information
You can find more information about it here.
There is article about that in 1.8 prelim docs.