Issue-17562 default DNS cluster addon service's name fix (#17563)

* Issue-17562 default DNS cluster addon service's name fix

* Clarified the cluster addon is CoreDNS with application name KubeDNS and corrected the links to enable CoreDNS instead of kube-dns. Also reverted the changes made in ID & ZH languages. Need help there

* Update content/en/docs/concepts/services-networking/connect-applications-service.md

Co-Authored-By: Tim Bannister <tim@scalefactory.com>
This commit is contained in:
Gireesh Puthumana
2019-11-20 06:13:19 +05:30
committed by Kubernetes Prow Robot
parent df3da58819
commit 55d80faab9
@@ -201,11 +201,8 @@ NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kube-dns ClusterIP 10.0.0.10 <none> 53/UDP,53/TCP 8m
```
If it isn't running, you can [enable it](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/kube-dns/README.md#how-do-i-configure-it).
The rest of this section will assume you have a Service with a long lived IP
(my-nginx), and a DNS server that has assigned a name to that IP (the CoreDNS
cluster addon), so you can talk to the Service from any pod in your cluster using
standard methods (e.g. gethostbyname). Let's run another curl application to test this:
(my-nginx), and a DNS server that has assigned a name to that IP. Here we use the CoreDNS cluster addon (application name `kube-dns`), so you can talk to the Service from any pod in your cluster using standard methods (e.g. `gethostbyname()`). If CoreDNS isn't running, you can enable it referring to the [CoreDNS README](https://github.com/coredns/deployment/tree/master/kubernetes) or [Installing CoreDNS](/docs/tasks/administer-cluster/coredns/#installing-coredns). Let's run another curl application to test this:
```shell
kubectl run curl --image=radial/busyboxplus:curl -i --tty