Skip to content

Instantly share code, notes, and snippets.

@Cryptophobia

Cryptophobia/helm-setup.md

Last active April 23, 2020 17:16
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Cryptophobia/271073b91cfdb01a10b60365509e183e to your computer and use it in GitHub Desktop.
Save Cryptophobia/271073b91cfdb01a10b60365509e183e to your computer and use it in GitHub Desktop.
Download ZIP
Helm Init GKE RBAC Hephy Workflow
Raw
helm-setup.md

Running Hephy Workflow on GKE Kubernetes Cluster Fix:

There is a fix for Helm that we need to do if we are using Helm 2.x in order to give helm enough permissions to create releases.

Hopefully this will be fixed in Helm 3.x as promised.

This is a known issue and was first found here: helm/helm#3055

Before we deploy Hephy Workflow, we need to enable our user to be able to create RBAC roles since Hephy Workflow needs to configure its own clusterroles through Helm:

Prerequisites for using Helm on GKE Role-Based Access Control:

$ kubectl create serviceaccount --namespace kube-system tiller
$ kubectl create clusterrolebinding tiller-cluster-rule --clusterrole=cluster-admin --serviceaccount=kube-system:tiller
$ helm init --upgrade --history-max=200 --service-account tiller

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment