From d5035a15e08ac3a78beea0b87b74ecc0badf486c Mon Sep 17 00:00:00 2001 From: Alexandros Mavrogiannis Date: Tue, 30 Jun 2015 15:58:21 -0700 Subject: [PATCH] Change factory name to client.NewInCluster The factory that generates a client for use within the cluster is NewInCluster, rather than NewInContainer. --- docs/accessing-the-cluster.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/accessing-the-cluster.md b/docs/accessing-the-cluster.md index 3497b5d5f1f..ac2e5be029a 100644 --- a/docs/accessing-the-cluster.md +++ b/docs/accessing-the-cluster.md @@ -113,7 +113,7 @@ From within a pod the recommended ways to connect to API are: kubernetes API to the localhost interface of the pod, so that other processes in any container of the pod can access it. See this [example of using kubectl proxy in a pod](../examples/kubectl-container/). - - use the Go client library, and create a client using the `client.NewInContainer()` factory. + - use the Go client library, and create a client using the `client.NewInCluster()` factory. This handles locating and authenticating to the apiserver. In each case, the credentials of the pod are used to communicate securely with the apiserver.