From 5f30df13b61e381dd61b96454715997a12ded916 Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Thu, 14 Mar 2019 11:01:43 -0700 Subject: [PATCH] kubeconfig fixes --- .../v2.x/en/k8s-in-rancher/kubeconfig/_index.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 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 65148c72058..8844c0f3962 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 @@ -17,22 +17,22 @@ For more information, see [Using kubectl to Access a Cluster]({{< baseurl >}}/ra >**Note:** By default, kubectl checks `~/.kube/config` for a kubeconfig file, but you can use any directory you want using the `--kubeconfig` flag. For example: >``` ->kubectl --kubeconfig /custom/path/kube.config get pods ->``` +kubectl --kubeconfig /custom/path/kube.config get pods +``` ## Accessing Rancher Launched Kubernetes clusters without Rancher server running By default, Rancher generates a kubeconfig file that will proxy through the Rancher server to connect to the Kubernetes API server on a cluster. -For [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters) clusters, which have _[authorized cluster endpoints]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options)_ enabled, Rancher generates extra context(s) in the kubeconfig file in order to connect directly to the cluster. +For [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters) clusters, which have _[authorized cluster endpoints]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options)_ enabled, Rancher generates extra context(s) in the kubeconfig file in order to connect directly to the cluster. -> **Note:** By default, all Rancher Launched Kubernetes clusters are enabled as _[authorized cluster endpoints]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options)_. +> **Note:** By default, all Rancher Launched Kubernetes clusters are enabled as _[authorized cluster endpoints]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/options)_. -To find the name of the context(s), view the kubeconfig file. +To find the name of the context(s), view the kubeconfig file. ### 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. +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. ``` # Assuming the kubeconfig file is located at ~/.kube/config @@ -44,7 +44,7 @@ kubectl --kubeconfig /custom/path/kube.config --context -fqdn get ### Clusters without FQDN defined as an Authorized Cluster Endpoint -If there is no FQDN defined for the cluster, extra contexts will be created referencing the IP address of each node in the control plane. Each context will be named `-`. When you want to use `kubectl` to access this cluster without Rancher, you will need to use this context. +If there is no FQDN defined for the cluster, extra contexts will be created referencing the IP address of each node in the control plane. Each context will be named `-`. When you want to use `kubectl` to access this cluster without Rancher, you will need to use this context. ``` # Assuming the kubeconfig file is located at ~/.kube/config