From 9020b24ce761fffa3015d894ccd5b9d8ca6cb1ab Mon Sep 17 00:00:00 2001 From: Alex Robinson Date: Tue, 24 May 2016 23:39:17 +0000 Subject: [PATCH] Fix local reference to section on constructing proxy URLs --- docs/user-guide/accessing-the-cluster.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/accessing-the-cluster.md b/docs/user-guide/accessing-the-cluster.md index eae63ed84e..8a5cc1739f 100644 --- a/docs/user-guide/accessing-the-cluster.md +++ b/docs/user-guide/accessing-the-cluster.md @@ -169,7 +169,7 @@ You have several options for connecting to nodes, pods and services from outside access to ports on the node IP, or for debugging. - Proxies may cause problems for some web applications. - Only works for HTTP/HTTPS. - - Described [here](#discovering-builtin-services). + - Described [here](#manually-constructing-apiserver-proxy-urls). - Access from a node or pod in the cluster. - Run a pod, and then connect to a shell in it using [kubectl exec](/docs/user-guide/kubectl/kubectl_exec). Connect to other nodes, pods, and services from that shell. @@ -275,4 +275,4 @@ There are several different proxies you may encounter when using Kubernetes: - implementation varies by cloud provider. Kubernetes users will typically not need to worry about anything other than the first two types. The cluster admin -will typically ensure that the latter types are setup correctly. \ No newline at end of file +will typically ensure that the latter types are setup correctly.