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

Merge pull request #1380 from dnoland1/patch-25

Browse Source 
kubectl to get context, instead of instructing user to look at config
This commit is contained in:
Denise
2019-04-12 14:36:12 -07:00
committed by GitHub
parent 8cb7a1ffdc e6961e7887
commit cdc819edee
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/cluster-admin/kubeconfig/_index.md
+8 -1
View File
@@ -30,7 +30,14 @@ For [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provis
> **Note:** By default, all Rancher Launched Kubernetes clusters have [Authorized Cluster Endpoint]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#authorized-cluster-endpoint) enabled. > **Note:** By default, all Rancher Launched Kubernetes clusters have [Authorized Cluster Endpoint]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/#authorized-cluster-endpoint) enabled.
To find the name of the context(s), view the kubeconfig file. To find the name of the context(s), run:
```
kubectl config get-contexts --kubeconfig /custom/path/kube.config
CURRENT NAME CLUSTER AUTHINFO NAMESPACE
* my-cluster my-cluster user-46tmn
my-cluster-controlplane-1 my-cluster-controlplane-1 user-46tmn
```
### Clusters with FQDN defined as an Authorized Cluster Endpoint ### Clusters with FQDN defined as an Authorized Cluster Endpoint