Fix local reference to section on constructing proxy URLs
This commit is contained in:
@@ -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.
|
access to ports on the node IP, or for debugging.
|
||||||
- Proxies may cause problems for some web applications.
|
- Proxies may cause problems for some web applications.
|
||||||
- Only works for HTTP/HTTPS.
|
- 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.
|
- 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).
|
- 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.
|
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.
|
- implementation varies by cloud provider.
|
||||||
|
|
||||||
Kubernetes users will typically not need to worry about anything other than the first two types. The cluster admin
|
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.
|
will typically ensure that the latter types are setup correctly.
|
||||||
|
|||||||
Reference in New Issue
Block a user