From 5b91603d693cb9fa3a160d758c1e8048d3c310a5 Mon Sep 17 00:00:00 2001
From: George G <git@gg7.io>
Date: Fri, 15 Jul 2016 15:47:01 +0100
Subject: [PATCH] scratch.md: kubeconfig should not embed the CA cert

---
 docs/getting-started-guides/scratch.md | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md
index 84f789a679..f1b222ae7e 100644
--- a/docs/getting-started-guides/scratch.md
+++ b/docs/getting-started-guides/scratch.md
@@ -280,7 +280,7 @@ users:
 clusters:
 - name: local
   cluster:
-    certificate-authority-data: ${CA_CERT_BASE64_ENCODED}
+    certificate-authority: /srv/kubernetes/ca.crt
 contexts:
 - context:
     cluster: local
@@ -289,10 +289,6 @@ contexts:
 current-context: service-account-context
 ```
 
-Where CA_CERT_BASE64_ENCODED can be generated like `< ca.crt base64
--w0`.  Alternatively you can refer to a file (e.g. `certificate-authority:
-/etc/kubernetes/ca.crt`).
-
 Put the kubeconfig(s) on every node.  The examples later in this
 guide assume that there are kubeconfigs in `/var/lib/kube-proxy/kubeconfig` and
 `/var/lib/kubelet/kubeconfig`.