First, install the helm tool on your mac:
1$ brew install kubernetes-helm
2==> Downloading https://homebrew.bintray.com/bottles/kubernetes-helm-2.14.1.mojave.bottle.tar.gz
3==> Downloading from https://akamai.bintray.com/5b/5baa398cf74033266bddd81709d0be52095ceab4f02d63b4f2a990545ea58c28?__gda__=exp=1561708889~hmac=8f6bd0379b36fbbd7eb58c6ff4fd3873ef36c79f4674f1ee2de10a9c9b374f48&response-content-disposition=attachment%
4######################################################################## 100.0%
5==> Pouring kubernetes-helm-2.14.1.mojave.bottle.tar.gz
6==> Caveats
7Bash completion has been installed to:
8 /usr/local/etc/bash_completion.d
9
10zsh completions have been installed to:
11 /usr/local/share/zsh/site-functions
12==> Summary
13🍺 /usr/local/Cellar/kubernetes-helm/2.14.1: 51 files, 91.6MB
Then, you need to create the tiller
service account:
1$ kubectl -n kube-system create serviceaccount tiller
2serviceaccount/tiller created
3```text
4Next, bind the `tiller` service account to the `cluster-admin` role:
5
6```shell
7$ kubectl create clusterrolebinding tiller --clusterrole cluster-admin --serviceaccount=kube-system:tiller
8clusterrolebinding.rbac.authorization.k8s.io/tiller created
After the install, you need to initialize the install:
1$ helm init --service-account tiller
2Creating /Users/myuser/.helm
3Creating /Users/myuser/.helm/repository
4Creating /Users/myuser/.helm/repository/cache
5Creating /Users/myuser/.helm/repository/local
6Creating /Users/myuser/.helm/plugins
7Creating /Users/myuser/.helm/starters
8Creating /Users/myuser/.helm/cache/archive
9Creating /Users/myuser/.helm/repository/repositories.yaml
10Adding stable repo with URL: https://kubernetes-charts.storage.googleapis.com
11Adding local repo with URL: http://127.0.0.1:8879/charts
12$HELM_HOME has been configured at /Users/pclaerhout/.helm.
13
14Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
15
16Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
17To prevent this, run `helm init` with the --tiller-tls-verify flag.
18For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
You can check if it's running by checking if the pod is running:
1$ kubectl get pods --namespace kube-system
2NAME READY STATUS RESTARTS AGE
3coredns-85c4d4c5d8-mvzrw 1/1 Running 0 68m
4coredns-85c4d4c5d8-slnh2 1/1 Running 0 60m
5coredns-autoscaler-7b6f68868f-hm5sv 1/1 Running 0 68m
6kube-proxy-dvlz9 1/1 Running 0 61m
7kube-proxy-rdbvf 1/1 Running 0 61m
8kube-proxy-zdk4h 1/1 Running 0 61m
9kubernetes-dashboard-6975779c8c-gs78v 1/1 Running 1 68m
10metrics-server-5dd76855f9-zsc84 1/1 Running 1 68m
11omsagent-6ffwk 1/1 Running 0 61m
12omsagent-h2skv 1/1 Running 0 61m
13omsagent-rs-676f95bc4b-jp8x7 1/1 Running 0 68m
14omsagent-tsfml 1/1 Running 0 61m
15tiller-deploy-9bf6fb76d-t5gmn 1/1 Running 0 46s
16tunnelfront-997bf4cdb-jjh2f 1/1 Running 0 68m
The official install guide can be found here.
If this post was enjoyable or useful for you, please share it! If you have comments, questions, or feedback, you can email my personal email. To get new posts, subscribe use the RSS feed.