Merge pull request #346 from rjeczalik/patch-1

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

docs: fix value name that disables rbac

**What this PR does / why we need it**:

Proper documentation for deploying cert-manager for k8s clusters without rbac enabled (happens to be the default for cdk on localhost).

**Which issue this PR fixes**

No issue per se, a follow-up on #256.
This commit is contained in:
jetstack-ci-bot 2018-02-25 20:20:05 +00:00 committed by GitHub
commit 0a0a2f3b13
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -40,7 +40,7 @@ $ helm install \
contrib/charts/cert-manager
```
> **NOTE**: if your cluster does not use RBAC (Role Based Access Control), you should add `--set rbac.create=false` when running your `helm install` command.
> **NOTE**: if your cluster does not use RBAC (Role Based Access Control), you should add `--set rbac.enabled=false` when running your `helm install` command.
The default cert-manager configuration is good for the majority of users, but a
full list of the available options can be found in the [Helm chart README](https://github.com/jetstack/cert-manager/blob/master/contrib/charts/cert-manager/README.md).
@ -51,7 +51,7 @@ issue certificates.
## Addendum
* If your cluster does not use RBAC, you should add `--set rbac.create=false` to
* If your cluster does not use RBAC, you should add `--set rbac.enabled=false` to
your `helm install` command. All RBAC related resources will not be created in
this instance.