From 489892d65d24face65093fc8e5a459b4c2c28ac0 Mon Sep 17 00:00:00 2001
From: George G <git@gg7.io>
Date: Fri, 15 Jul 2016 14:37:44 +0100
Subject: [PATCH] scratch.md: Clarify CA_CERT_BASE64_ENCODED /
 certificate-authority

---
 docs/getting-started-guides/scratch.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md
index a571e21845..d9e1a561d1 100644
--- a/docs/getting-started-guides/scratch.md
+++ b/docs/getting-started-guides/scratch.md
@@ -288,6 +288,10 @@ 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`.