Kube config warnings for code execution (#28248)

* Update configure-access-multiple-clusters.md

* Rewording kubeconfig warning

* Tabitha's suggestion

Co-authored-by: Tabitha Sable <[email protected]>

* Re-order sentences

* Copy update

Co-authored-by: Tabitha Sable <[email protected]>

Author: gracenng

content/en/docs/concepts/configuration/organize-cluster-access-kubeconfig.md

@@ -17,6 +17,11 @@ a *kubeconfig file*. This is a generic way of referring to configuration files.
 It does not mean that there is a file named `kubeconfig`.
 {{< /note >}}
 
+{{< warning >}}
+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.
+{{< /warning>}}
+
 By default, `kubectl` looks for a file named `config` in the `$HOME/.kube` directory.
 You can specify other kubeconfig files by setting the `KUBECONFIG` environment
 variable or by setting the
@@ -154,4 +159,3 @@ are stored absolutely.
 
 
 
-

content/en/docs/tasks/access-application-cluster/configure-access-multiple-clusters.md

@@ -20,6 +20,13 @@ a *kubeconfig file*. This is a generic way of referring to configuration files.
 It does not mean that there is a file named `kubeconfig`.
 {{< /note >}}
 
+
+{{< warning >}}
+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.
+{{< /warning>}}
+
+
 ## {{% heading "prerequisites" %}}
 
 {{< include "task-tutorial-prereqs.md" >}}