From edbbf971e148f20f2a84faf772de64286e35f339 Mon Sep 17 00:00:00 2001 From: Jordan Liggitt Date: Thu, 26 Apr 2018 14:51:27 -0400 Subject: [PATCH] Update with qualified kuberenetes service DNS name (#8166) --- docs/tasks/access-application-cluster/access-cluster.md | 2 +- docs/tasks/administer-cluster/access-cluster-api.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/tasks/access-application-cluster/access-cluster.md b/docs/tasks/access-application-cluster/access-cluster.md index a2826fb49d..9b50daf05a 100644 --- a/docs/tasks/access-application-cluster/access-cluster.md +++ b/docs/tasks/access-application-cluster/access-cluster.md @@ -151,7 +151,7 @@ When accessing the API from a pod, locating and authenticating to the apiserver are somewhat different. The recommended way to locate the apiserver within the pod is with -the `kubernetes` DNS name, which resolves to a Service IP which in turn +the `kubernetes.default.svc` DNS name, which resolves to a Service IP which in turn will be routed to an apiserver. The recommended way to authenticate to the apiserver is with a diff --git a/docs/tasks/administer-cluster/access-cluster-api.md b/docs/tasks/administer-cluster/access-cluster-api.md index f107183500..04e01898a7 100644 --- a/docs/tasks/administer-cluster/access-cluster-api.md +++ b/docs/tasks/administer-cluster/access-cluster-api.md @@ -177,7 +177,7 @@ libraries can automatically discover the API server and authenticate. While running in a Pod, the Kubernetes apiserver is accessible via a Service named `kubernetes` in the `default` namespace. Therefore, Pods can use the -`kubernetes.default` hostname to query the API server. Official client libraries +`kubernetes.default.svc` hostname to query the API server. Official client libraries do this automatically. From within a Pod, the recommended way to authenticate to the API server is with a