From 8a87da7a8e87154d9c761dc856b81d2335617765 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Tue, 3 Dec 2019 15:28:48 -0700 Subject: [PATCH] Remove outdated Helm information --- content/rancher/v2.x/en/overview/concepts/_index.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/rancher/v2.x/en/overview/concepts/_index.md b/content/rancher/v2.x/en/overview/concepts/_index.md index c7d848f88da..f4fe9fc26f0 100644 --- a/content/rancher/v2.x/en/overview/concepts/_index.md +++ b/content/rancher/v2.x/en/overview/concepts/_index.md @@ -69,8 +69,4 @@ For high-availability installations of Rancher, Helm is the tool used to install Helm is the package management tool of choice for Kubernetes. Helm charts provide templating syntax for Kubernetes YAML manifest documents. With Helm we can create configurable deployments instead of just using static files. For more information about creating your own catalog of deployments, check out the docs at [https://helm.sh/](https://helm.sh). -To be able to use Helm, the server-side component `tiller` needs to be installed on your cluster. Helm installs the `tiller` service on your cluster to manage charts because Helm cannot manipulate Kubernetes resources directly. - -Because Rancher Kubernetes Engine enables role-based access control by default, the `tiller` service needs to be given permission to manipulate Kubernetes resources. Therefore, the high-availability Rancher installation instructions show you how to use `kubectl` to create a `serviceaccount` and `clusterrolebinding` so that `tiller` has permission to deploy Rancher on the cluster. - For more information on service accounts and cluster role binding, refer to the [Kubernetes documentation.](https://kubernetes.io/docs/reference/access-authn-authz/rbac/) \ No newline at end of file