$ cat ~/helm-rbac.yaml
apiVersion: v1
kind: ServiceAccount
metadata:
name: tiller
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
name: tiller
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: ClusterRole
name: cluster-admin
subjects:
- kind: ServiceAccount
name: tiller
namespace: kube-system
$ kubectl apply -f ~/helm-rbac.yaml
$ helm init --service-account=tiller
$HELM_HOME has been configured at /home/aric/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
$ helm ls
error: error upgrading connection: Upgrade request required
$ kubectl get all -n kube-system
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
ds/canal 7 7 7 7 7 <none> 2h
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
deploy/kube-dns 2 2 2 2 2h
deploy/kube-dns-autoscaler 1 1 1 1 2h
deploy/tiller-deploy 1 1 1 1 33m
NAME DESIRED CURRENT READY AGE
rs/kube-dns-5ccb66df65 2 2 2 2h
rs/kube-dns-autoscaler-6c4b786f5 1 1 1 2h
rs/tiller-deploy-f9b8476d 1 1 1 33m
NAME DESIRED SUCCESSFUL AGE
jobs/rke-ingress-controller-deploy-job 1 1 2h
jobs/rke-kubedns-addon-deploy-job 1 1 2h
jobs/rke-network-plugin-deploy-job 1 1 2h
NAME READY STATUS RESTARTS AGE
po/canal-6kjl9 3/3 Running 0 2h
po/canal-btbkh 3/3 Running 0 2h
po/canal-nspkm 3/3 Running 0 2h
po/canal-s9pjb 3/3 Running 0 2h
po/canal-sdgx2 3/3 Running 0 2h
po/canal-vfkfv 3/3 Running 0 2h
po/canal-whxnz 3/3 Running 0 2h
po/kube-dns-5ccb66df65-7tgfp 3/3 Running 0 2h
po/kube-dns-5ccb66df65-lpshb 3/3 Running 0 2h
po/kube-dns-autoscaler-6c4b786f5-8c84n 1/1 Running 0 2h
po/tiller-deploy-f9b8476d-m95gr 1/1 Running 0 33m
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
svc/kube-dns ClusterIP 10.43.0.10 <none> 53/UDP,53/TCP 2h
svc/tiller-deploy ClusterIP 10.43.48.253 <none> 44134/TCP 33m
NOTE: Also works with NodePort!
$ helm init --service-account=tiller --net-host
$HELM_HOME has been configured at /home/aric/.helm.
Tiller (the Helm server-side component) has been installed into your Kubernetes Cluster.
Please note: by default, Tiller is deployed with an insecure 'allow unauthenticated users' policy.
For more information on securing your installation see: https://docs.helm.sh/using_helm/#securing-your-helm-installation
Happy Helming!
$ export HELM_HOST=172.17.4.43:44134
$ helm ls
$
NOTE: helm ls returns nothing since this is a new helm installation.
$ helm install stable/mysql
NAME: unhinged-peacock
LAST DEPLOYED: Fri Aug 3 13:59:59 2018
NAMESPACE: default
STATUS: DEPLOYED
RESOURCES:
==> v1beta1/Deployment
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
unhinged-peacock-mysql 1 1 1 0 0s
==> v1/Pod(related)
NAME READY STATUS RESTARTS AGE
unhinged-peacock-mysql-5587558bf8-h4xjc 0/1 Pending 0 0s
==> v1/Secret
NAME TYPE DATA AGE
unhinged-peacock-mysql Opaque 2 0s
==> v1/PersistentVolumeClaim
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
unhinged-peacock-mysql Pending 0s
==> v1/Service
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
unhinged-peacock-mysql ClusterIP 10.43.62.80 <none> 3306/TCP 0s
NOTES:
MySQL can be accessed via port 3306 on the following DNS name from within your cluster:
unhinged-peacock-mysql.default.svc.cluster.local