Consider renaming the Kubernetes DNS service from `coredns` to `kube-dns`

[weiiwang01]

Summary

Please consider renaming the Kubernetes DNS service to kube-dns.
Currently, the Kubernetes DNS service is named coredns.

k8s kubectl get services -n kube-system
NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)         AGE
...
coredns                             ClusterIP   10.152.183.94    <none>        53/UDP,53/TCP   126m
...

Why is this important?

Usually the Kubernetes DNS service is conventionally named kube-dns, even when the DNS provider is not kube-dns. This is for compatibility reasons. Here’s the quote from the Kubernetes documentation:

The CoreDNS Service is named kube-dns in the metadata.name field.
The intent is to ensure greater interoperability with workloads that relied on the legacy kube-dns Service name to resolve addresses internal to the cluster. Using a Service named kube-dns abstracts away the implementation detail of which DNS provider is running behind that common name.

Are you interested in contributing to this feature?

Yes

[bschimke95]

Hey @weiiwang01
Thanks for bringing that to our attention.
We agree that the snap should stick to that convention with microk8s we also follow it.

We will need to figure out the best way to ensure a smooth upgrade path if people upgrade there cluster and likely fix this in the upcoming pulse.