whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #33429 from reylejano/followup-31527-socks5

Browse Source 
Update SOCKS5 page, follow-up to pr 31527
This commit is contained in:
Kubernetes Prow Robot
2022-05-03 22:31:30 -07:00
committed by GitHub
parent 48934ab197 0bdd4d2d03
commit 0678ae692b
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/extend-kubernetes/socks5-proxy-access-api.md
+3 -3
View File
@@ -15,8 +15,8 @@ This is useful when the cluster you want to access does not expose its API direc
{{< include "task-tutorial-prereqs.md" >}} {{< version-check >}} {{< include "task-tutorial-prereqs.md" >}} {{< version-check >}}
You need SSH client software (the `ssh` tool), and an SSH server running on the remote server. You need SSH client software (the `ssh` tool), and an SSH service running on the remote server.
You must be able to log in to the SSH server on the remote server. You must be able to log in to the SSH service on the remote server.
<!-- steps --> <!-- steps -->
@@ -29,7 +29,7 @@ You can instead use any other kind of [SOCKS5](https://en.wikipedia.org/wiki/SOC
Figure 1 represents what you're going to achieve in this task. Figure 1 represents what you're going to achieve in this task.
* You have a client computer from where you're going to create requests to talk to the Kubernetes API * You have a client computer, referred to as local in the steps ahead, from where you're going to create requests to talk to the Kubernetes API.
* The Kubernetes server/API is hosted on a remote server. * The Kubernetes server/API is hosted on a remote server.
* You will use SSH client and server software to create a secure SOCKS5 tunnel between the local and * You will use SSH client and server software to create a secure SOCKS5 tunnel between the local and
the remote server. The HTTPS traffic between the client and the Kubernetes API will flow over the SOCKS5 the remote server. The HTTPS traffic between the client and the Kubernetes API will flow over the SOCKS5