Update with qualified kuberenetes service DNS name (#8166)
This commit is contained in:
parent
f56b4f4b41
commit
edbbf971e1
|
|
@ -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
|
||||
|
|
|
|||
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Reference in New Issue