From 7febf3e780a1d27bacd55905182b9a9929a79838 Mon Sep 17 00:00:00 2001 From: Andrew Chen Date: Tue, 1 Aug 2017 22:37:46 -0700 Subject: [PATCH] add template tags --- .../authenticate-across-clusters-kubeconfig.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md b/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md index 3f99bd5cd4..a8ec6b55f9 100644 --- a/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md +++ b/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md @@ -2,6 +2,7 @@ title: Authenticate across clusters with kubeconfig --- +{% capture overview %} Authentication in Kubernetes can differ for different individuals. - A running kubelet might have one way of authenticating (i.e. certificates). @@ -14,11 +15,13 @@ So in order to easily switch between multiple clusters, for multiple users, a ku This file contains a series of authentication mechanisms and cluster connection information associated with nicknames. It also introduces the concept of a tuple of authentication information (user) and cluster connection information called a context that is also associated with a nickname. Multiple kubeconfig files are allowed, if specified explicitly. At runtime they are loaded and merged along with override options specified from the command line (see [rules](#loading-and-merging-rules) below). +{% endcapture %} -## Related discussion - -[http://issue.k8s.io/1755](http://issue.k8s.io/1755) +{% capture prerequisites %} +* {% include task-tutorial-prereqs.md %} +{% endcapture %} +{% capture steps %} ## Components of a kubeconfig file ### Example kubeconfig file @@ -298,7 +301,9 @@ $ kubectl config set-context queen-anne-context --cluster=pig-cluster --user=bla $ kubectl config set-context federal-context --cluster=horse-cluster --user=green-user --namespace=chisel-ns $ kubectl config use-context federal-context ``` +{% endcapture %} +{% capture discussion %} ### Final notes for tying it all together So, tying this all together, a quick start to create your own kubeconfig file: @@ -309,4 +314,8 @@ So, tying this all together, a quick start to create your own kubeconfig file: - Make sure your api-server provides at least one set of credentials (for example, `green-user`) when launched. You will of course have to look at api-server documentation in order to determine the current state-of-the-art in terms of providing authentication details. +## Related discussion +[http://issue.k8s.io/1755](http://issue.k8s.io/1755) +{% endcapture %} + {% include templates/task.md %}