All platforms need to work with Helm 3 (in addition to Helm 2)

[viccuad]

Hello.

Problem

For KubeCF (and CAP 2.0 then) all platforms should deploy with Helm 3. Right now, the terraform scripts fail because the helm provider that we are using is for Helm 2.

We need to keep both Helm 2 and Helm 3 terraform scripts around, to be able to deploy CAP 1.X and CAP 2.X though.

Workaround

For now, we are deploying as it is with Helm 2 with cap-terraform, and then reusing the kubeconfig on a folder with Helm 3. With catapult: BACKEND={gke,eks} make k8s which we have pinned to Helm 2, and then, HELM_VERSION=v3.3.1 BACKEND={gke,eks} make kubeconfig locally and on pipelines. This leaves Tiller pods on the deployment, for which we don't care for now.

[satadruroy]

#51

Until it's reviewed/merged you can work from the branch sr/move-to-helm3

[satadruroy]

One further comment - with this change, for people that want to deploy SCF based on these templates it will be helm3 only - both myself and @troytop have tested it and we can confirm it works.

So, these templates will now work for both SCF and KubeCF deployments - I did not want to retain helm2 support as we can avoid all the security implications of tiller and its usage with cluster-admin role.

@bear454 fyi