diff --git a/docs/quickstart.md b/docs/quickstart.md
index ef3cb460e..d7f2e3b91 100644
--- a/docs/quickstart.md
+++ b/docs/quickstart.md
@@ -54,9 +54,11 @@ Once you have Helm ready, you can initialize the local CLI and also
 install Tiller into your Kubernetes cluster in one step:
 
 ```console
-$ helm init
+$ helm init --max-history 200
 ```
 
+**TIP:** Setting `--max-history` on helm init is recommended as configmaps and other objects in helm history can grow large in number if not purged by max limit. Without a max history set the history is kept indefinitely, leaving a large number of records for helm and tiller to maintain.
+
 This will install Tiller into the Kubernetes cluster you saw with
 `kubectl config current-context`.
 
diff --git a/docs/rbac.md b/docs/rbac.md
index 4b39ecdc6..45371cda8 100644
--- a/docs/rbac.md
+++ b/docs/rbac.md
@@ -43,7 +43,7 @@ _Note: The cluster-admin role is created by default in a Kubernetes cluster, so
 $ kubectl create -f rbac-config.yaml
 serviceaccount "tiller" created
 clusterrolebinding "tiller" created
-$ helm init --service-account tiller
+$ helm init --service-account tiller --max-history 200
 ```
 
 ### Example: Deploy Tiller in a namespace, restricted to deploying resources only in that namespace