From b0eb40b2ca67146b7bb76e0197bfba0c83c5dd60 Mon Sep 17 00:00:00 2001
From: Colin Dickson <colin.dickson@gmail.com>
Date: Thu, 19 Apr 2018 19:20:42 -0400
Subject: [PATCH] fixed flag for tls ca cert option in the documentation

---
 docs/securing_installation.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/securing_installation.md b/docs/securing_installation.md
index 5c420242e..9f74f6049 100644
--- a/docs/securing_installation.md
+++ b/docs/securing_installation.md
@@ -95,10 +95,10 @@ If these steps are followed, an example `helm init` command might look something
 $ helm init \
 --tiller-tls \
 --tiller-tls-verify \
---tiller-tls-ca-cert=ca.pem \
 --tiller-tls-cert=cert.pem \
 --tiller-tls-key=key.pem \
---service-account=accountname  
+--tls-ca-cert=ca.pem \
+--service-account=accountname
 ```
 
 This command will start Tiller with both strong authentication over gRPC, and a service account to which RBAC policies have been applied.