Skip to content
This repository has been archived by the owner on Sep 21, 2021. It is now read-only.

Commit

Permalink
Fix role.yaml link in 2000-01-07-kubernetes.md
Browse files Browse the repository at this point in the history
  • Loading branch information
ortex authored and diemol committed Dec 9, 2019
1 parent 905b99b commit d04b227
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/_posts/2000-01-07-kubernetes.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,7 +77,7 @@ uses role based authentication by default, meaning that the service account will
the Kubernetes API that it needs to.

By default, the helm chart will create a `ServiceAccount` with an appropriate `Role` and `RoleBinding` at the namespace level.
You can see the `Role` that will be created [here](https://github.com/zalando/zalenium/tree/master/charts/zalenium/template/role.yaml){:target="_blank"}.
You can see the `Role` that will be created [here](https://github.com/zalando/zalenium/tree/master/charts/zalenium/templates/role.yaml){:target="_blank"}.

If your cluster does not have RBAC enabled, you can disable it with `--set rbac.create=false` and `--set serviceAccount.create=false`.
You can also use a predefined `ServiceAccount` with `--set rbac.create=false` and `--set serviceAccount.create=false` and `--set serviceAccount.name=foo`.
Expand Down

0 comments on commit d04b227

Please sign in to comment.