public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-16 01:53:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

Cleanup helm/tiller + added verification steps for helm/tiller

Browse Source
This commit is contained in:
Sebastiaan van Steenis
2018-10-17 16:35:16 +02:00
committed by Denise Schannon
parent 8ac7963c6f
commit 28daf4dc16
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/ha/helm-init/_index.md
+8
View File
@@ -3,7 +3,11 @@ title: 3 - Initialize Helm (Install tiller)
weight: 195
---
<<<<<<< HEAD
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 repository 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 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.
>>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller
> **Note:** For systems without direct internet access see [Helm - Air Gap]({{< baseurl >}}/rancher/v2.x/en/installation/air-gap-installation/install-rancher/#helm) for install details.
@@ -12,7 +16,11 @@ Helm is the package management tool of choice for Kubernetes. Helm charts provid
Helm installs the `tiller` service on your cluster to manage charts. Since RKE enables RBAC by default we will need to use `kubectl` to create a `serviceaccount` and `clusterrolebinding` so `tiller` has permission to deploy to the cluster.
* Create the `ServiceAccount` in the `kube-system` namespace.
<<<<<<< HEAD
* Create the `ClusterRoleBinding` to give the `tiller` service account access to the cluster.
=======
* Create the `ClusterRoleBinding` to give the `tiller` account access to the cluster.
>>>>>>> Cleanup helm/tiller + added verification steps for helm/tiller
* Finally use `helm` to install the `tiller` service
```plain