public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 12:38:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

Revert hint added in 0475d47e and d7f9ab67. Linked section does not exist in 2.5

Browse Source 
Also remove duplicate period
This commit is contained in:
Billy Tat
2023-04-18 14:32:37 -07:00
parent d7f9ab67cc
commit d164b53d70
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.5/how-to-guides/advanced-user-guides/manage-clusters/access-clusters/use-kubectl-and-kubeconfig.md
+1 -3
View File
@@ -46,9 +46,7 @@ This method is only available for RKE clusters that have the [authorized cluster
We recommend that as a best practice, you should set up this method to access your RKE cluster, so that just in case you can’t connect to Rancher, you can still access the cluster.
> **Prerequisites:** The following steps assume that you have created a Kubernetes cluster and followed the steps to [connect to your cluster with kubectl from your workstation.](#accessing-clusters-with-kubectl-from-your-workstation).
>
> On RKE2 and K3s clusters, you need to [manually enable](../../../new-user-guides/kubernetes-clusters-in-rancher-setup/register-existing-clusters.md#authorized-cluster-endpoint-support-for-rke2-and-k3s-clusters) authorized cluster endpoints.
> **Prerequisites:** The following steps assume that you have created a Kubernetes cluster and followed the steps to [connect to your cluster with kubectl from your workstation](#accessing-clusters-with-kubectl-from-your-workstation).
To find the name of the context(s) in your downloaded kubeconfig file, run: