From 6ddd8b2c94b4140426e2cc76e56cde0332c3523e Mon Sep 17 00:00:00 2001 From: Denise Date: Tue, 12 Mar 2019 15:10:28 -0700 Subject: [PATCH] Update _index.md --- content/rancher/v2.x/en/k8s-in-rancher/kubeconfig/_index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/rancher/v2.x/en/k8s-in-rancher/kubeconfig/_index.md b/content/rancher/v2.x/en/k8s-in-rancher/kubeconfig/_index.md index 184a03f8e68..65148c72058 100644 --- a/content/rancher/v2.x/en/k8s-in-rancher/kubeconfig/_index.md +++ b/content/rancher/v2.x/en/k8s-in-rancher/kubeconfig/_index.md @@ -30,8 +30,6 @@ For [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provis To find the name of the context(s), view the kubeconfig file. -See [Cluster Options for Provisioning RKE in Rancher]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options/) and [RKE Config Options]({{< baseurl >}}/rke/v0.1.x/en/config-options/authentication/) for more information on user authentication in a cluster. - ### Clusters with FQDN defined as an Authorized Cluster Endpoint If an FQDN is defined for the cluster, a single context referencing the FQDN will be created. The context will be named `-fqdn`. When you want to use `kubectl` to access this cluster without Rancher, you will need to use this context.