From 700bb5564b53f04624b0e60ad3db2e76e915f960 Mon Sep 17 00:00:00 2001 From: zacharysarah Date: Tue, 1 Aug 2017 15:34:50 -0700 Subject: [PATCH] Add task template --- .../authenticate-across-clusters-kubeconfig.md | 7 +++---- 1 file changed, 3 insertions(+), 4 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 44e0ff5420..d0cadc23e1 100644 --- a/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md +++ b/docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig.md @@ -1,8 +1,5 @@ --- -assignees: -- mikedanese -- thockin -title: Authenticate Across Clusters with kubeconfig +title: Authenticate across clusters with kubeconfig --- Authentication in Kubernetes can differ for different individuals. @@ -311,3 +308,5 @@ So, tying this all together, a quick start to create your own kubeconfig file: - Replace the snippet above with information for your cluster's api-server endpoint. - Make sure your api-server is launched in such a way that at least one user (for example, green-user) credentials are provided to it. 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. + +{% include templates/task.md %}