Skip to content
Permalink
Browse files

Fix "helm init" parameters

In the quickstart guide, --max-history is recommended as parameter for helm init. The actual name of the parameter is --history-max.

Signed-off-by: Jens Frank <jf@mormo.org>
  • Loading branch information...
JeLuF committed Mar 11, 2019
1 parent 367b6fc commit b480badd05ad01006363763c92b5394cdc5fc9c4
Showing with 3 additions and 3 deletions.
  1. +2 −2 docs/quickstart.md
  2. +1 −1 docs/rbac.md
@@ -54,10 +54,10 @@ 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 --max-history 200
$ helm init --history-max 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.
**TIP:** Setting `--history-max` 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`.
@@ -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 --max-history 200
$ helm init --service-account tiller --history-max 200
```

### Example: Deploy Tiller in a namespace, restricted to deploying resources only in that namespace

0 comments on commit b480bad

Please sign in to comment.
You can’t perform that action at this time.