From 01043efa7e40b0432f92db434c5dde57fb7f9c5b Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Tue, 18 Oct 2016 11:01:46 +0100 Subject: [PATCH] Update out-of-date text about creating a client --- docs/user-guide/accessing-the-cluster.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/accessing-the-cluster.md b/docs/user-guide/accessing-the-cluster.md index 63134b4909..b08dfa8eb6 100644 --- a/docs/user-guide/accessing-the-cluster.md +++ b/docs/user-guide/accessing-the-cluster.md @@ -182,9 +182,8 @@ 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](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/examples/kubectl-container/). - - use the Go client library, and create a client using the `client.NewInCluster()` factory. - This handles locating and authenticating to the apiserver. See this [example of using Go client - library in a pod](https://github.com/kubernetes/client-go/blob/master/examples/in-cluster/main.go). + - use the Go client library, and create a client using the `rest.InClusterConfig()` and `kubernetes.NewForConfig()` functions. + They handle locating and authenticating to the apiserver. [example](https://github.com/kubernetes/client-go/blob/master/examples/in-cluster/main.go) In each case, the credentials of the pod are used to communicate securely with the apiserver.