whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update with qualified kuberenetes service DNS name (#8166)

Browse Source
This commit is contained in:
Jordan Liggitt
2018-04-26 14:51:27 -04:00
committed by k8s-ci-robot
parent f56b4f4b41
commit edbbf971e1
2 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/tasks/access-application-cluster/access-cluster.md
+1 -1
View File
@@ -151,7 +151,7 @@ When accessing the API from a pod, locating and authenticating
to the apiserver are somewhat different. to the apiserver are somewhat different.
The recommended way to locate the apiserver within the pod is with 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. will be routed to an apiserver.
The recommended way to authenticate to the apiserver is with a The recommended way to authenticate to the apiserver is with a
docs/tasks/administer-cluster/access-cluster-api.md
+1 -1
View File
@@ -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 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` 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. do this automatically.
From within a Pod, the recommended way to authenticate to the API server is with a From within a Pod, the recommended way to authenticate to the API server is with a