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

Docs fix for kubectl proxy configuration

Browse Source 
Follow-up to https://github.com/kubernetes/website/pull/32245
This commit is contained in:
Chris Burgess
2022-04-13 21:05:08 +12:00
parent 6893daac26
commit 81fe9b4e91
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/configuration/organize-cluster-access-kubeconfig.md
+3 -3
View File
@@ -18,7 +18,7 @@ It does not mean that there is a file named `kubeconfig`.
{{< /note >}} {{< /note >}}
{{< warning >}} {{< warning >}}
Only use kubeconfig files from trusted sources. Using a specially-crafted kubeconfig file could result in malicious code execution or file exposure. Only use kubeconfig files from trusted sources. Using a specially-crafted kubeconfig file could result in malicious code execution or file exposure.
If you must use an untrusted kubeconfig file, inspect it carefully first, much as you would a shell script. If you must use an untrusted kubeconfig file, inspect it carefully first, much as you would a shell script.
{{< /warning>}} {{< /warning>}}
@@ -53,7 +53,7 @@ clusters and namespaces.
A *context* element in a kubeconfig file is used to group access parameters A *context* element in a kubeconfig file is used to group access parameters
under a convenient name. Each context has three parameters: cluster, namespace, and user. under a convenient name. Each context has three parameters: cluster, namespace, and user.
By default, the `kubectl` command-line tool uses parameters from By default, the `kubectl` command-line tool uses parameters from
the *current context* to communicate with the cluster. the *current context* to communicate with the cluster.
To choose the current context: To choose the current context:
``` ```
@@ -167,7 +167,7 @@ users:
contexts: contexts:
- context: - context:
name: development name: development
``` ```