From 586fd88b02a1bac81d9e8a42ef71e327dcdbf88f Mon Sep 17 00:00:00 2001 From: DeltaX Date: Sun, 21 Jan 2024 15:58:46 +0800 Subject: [PATCH] Fix access-cluster-services.md list indent --- .../tasks/access-application-cluster/access-cluster-services.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/access-application-cluster/access-cluster-services.md b/content/en/docs/tasks/access-application-cluster/access-cluster-services.md index afc8f50823dba..652c253fb0a5b 100644 --- a/content/en/docs/tasks/access-application-cluster/access-cluster-services.md +++ b/content/en/docs/tasks/access-application-cluster/access-cluster-services.md @@ -43,7 +43,7 @@ You have several options for connecting to nodes, pods and services from outside - Proxies may cause problems for some web applications. - Only works for HTTP/HTTPS. - 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/reference/generated/kubectl/kubectl-commands/#exec). Connect to other nodes, pods, and services from that shell. - Some clusters may allow you to ssh to a node in the cluster. From there you may be able to