Skip to content

Commit 9f830f8

Browse files
authored
Merge pull request kubernetes#6713 from ahmetb/delete-kubectl-container
access-cluster.md: scrub kubectl-container references
2 parents 9a53591 + 117d8ec commit 9f830f8

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

docs/tasks/access-application-cluster/access-cluster.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ the `kubernetes` DNS name, which resolves to a Service IP which in turn
155155
will be routed to an apiserver.
156156

157157
The recommended way to authenticate to the apiserver is with a
158-
[service account](/docs/tasks/configure-pod-container/configure-service-account/) credential. By kube-system, a pod
158+
[service account](/docs/tasks/configure-pod-container/configure-service-account/) credential. By kube-system, a pod
159159
is associated with a service account, and a credential (token) for that
160160
service account is placed into the filesystem tree of each container in that pod,
161161
at `/var/run/secrets/kubernetes.io/serviceaccount/token`.
@@ -169,17 +169,15 @@ at `/var/run/secrets/kubernetes.io/serviceaccount/namespace` in each container.
169169

170170
From within a pod the recommended ways to connect to API are:
171171

172-
- run a kubectl proxy as one of the containers in the pod, or as a background
173-
process within a container. This proxies the
172+
- run `kubectl proxy` in a sidecar container in the pod, or as a background
173+
process within the container. This proxies the
174174
Kubernetes API to the localhost interface of the pod, so that other processes
175-
in any container of the pod can access it. See this [example of using kubectl proxy
176-
in a pod](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/staging/kubectl-container/).
175+
in any container of the pod can access it.
177176
- use the Go client library, and create a client using the `rest.InClusterConfig()` and `kubernetes.NewForConfig()` functions.
178177
They handle locating and authenticating to the apiserver. [example](https://git.k8s.io/client-go/examples/in-cluster-client-configuration/main.go)
179178

180179
In each case, the credentials of the pod are used to communicate securely with the apiserver.
181180

182-
183181
## Accessing services running on the cluster
184182

185183
The previous section was about connecting the Kubernetes API server. This section is about

0 commit comments

Comments
 (0)