From c2c95999f39928f5e5c77621a010565b8f52f9be Mon Sep 17 00:00:00 2001 From: Chris Kim Date: Mon, 19 Sep 2016 17:31:01 -0400 Subject: [PATCH] Fix typo in kubeconfig-file.md --- docs/user-guide/kubeconfig-file.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/kubeconfig-file.md b/docs/user-guide/kubeconfig-file.md index 043b6cc002..3db16e17de 100644 --- a/docs/user-guide/kubeconfig-file.md +++ b/docs/user-guide/kubeconfig-file.md @@ -307,8 +307,8 @@ $ kubectl config use-context federal-context So, tying this all together, a quick start to creating your own kubeconfig file: -- Take a good look and understand how you're api-server is being launched: You need to know YOUR security requirements and policies before you can design a kubeconfig file for convenient authentication. +- Take a good look and understand how your api-server is being launched: You need to know YOUR security requirements and policies before you can design a kubeconfig file for convenient authentication. - 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 (i.e. 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. \ No newline at end of file +- Make sure your api-server is launched in such a way that at least one user (i.e. 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.