Migrate to Helm 3.0 (2.x deprecation in November 2020)

[arm4b]

Helm v3.0 GA was released in Nov 2019 https://helm.sh/blog/helm-3-released/

While at the moment we'd prefer to pin Helm 2.x, consider migrating to 3.x when it'll stabilize a little bit and see what involves for us to rely on latest Helm.

[rahulparihar270992]

Hi @armab , hope you are doing well ? As you have added migrate to helm 3.0 feature for stackstorm . Do you have any initial thoughts how you are going to take it forward ? If i am correct i have made change in https://github.com/StackStorm/stackstorm-ha/blob/master/.circleci/config.yml#L20 file to point helm version 3.0.0 . but still getting issue as
helm install stackstorm-ha/ --generate-name
Error: found in Chart.yaml, but missing in charts/ directory: rabbitmq-ha, mongodb-replicaset, external-dns, etcd-operator Do you have any pointers for this?

[arm4b]

These are 3rd party Helm charts stackstorm-ha relies on https://github.com/helm/charts/blob/master/stable/

From the message above, looks like in order to switch to Helm 3.0 those upstream dependencies needs to be migrated first.
See https://github.com/helm/charts/blob/master/stable/rabbitmq-ha/Chart.yaml#L2 which still references previous Helm API Version.

[wantdrink]

Hi @armab, I installed rabbitmq-ha-1.36.4 first with helm 3.0 and it succeeded:

NAMESPACE NAME READY STATUS RESTARTS AGE IP
default my-rabbit-rabbitmq-ha-0 1/1 Running 1 2d8h 10.244.3.29
default my-rabbit-rabbitmq-ha-1 1/1 Running 1 2d8h 10.244.1.24
default my-rabbit-rabbitmq-ha-2 1/1 Running 1 2d8h 10.244.2.14

So does it mean this chart works in helm 3.
But if install ss ha with :
helm install stackstorm -n st2 -f values.yaml .

The error is:

manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "EtcdCluster" in version "etcd.database.coreos.com/v1beta2"

[arm4b]

That part is coming from the "etcd-operator" dependency from the official Helm charts repository.

Relevant answer from similar kubernetes-retired/kubefed#1143 (comment):

[wantdrink]

@armab Thanks. So the left is etcd-operator's issue. Let's wait for it to be updated to support helm 3.

[rahulparihar270992]

These are 3rd party Helm charts stackstorm-ha relies on https://github.com/helm/charts/blob/master/stable/

From the message above, looks like in order to switch to Helm 3.0 those upstream dependencies needs to be migrated first.
See https://github.com/helm/charts/blob/master/stable/rabbitmq-ha/Chart.yaml#L2 which still references previous Helm API Version.

Thanks @armab and @wantdrink for replying back . have tried to make changes in https://github.com/rahulparihar270992/charts repo as belows https://github.com/rahulparihar270992/charts/blob/master/stable/rabbitmq-ha/Chart.yaml#L2 . and tried to changed requirements.yml as https://github.com/rahulparihar270992/stackstorm-ha/blob/feature/stackstome-v1/requirements.yaml#L4 . Not sure this is the right pointing to stable dependencies ? Do you have any suggestion how it going to work? Still facing similar issue.
Error: found in Chart.yaml, but missing in charts/ directory: rabbitmq-ha, mongodb-replicaset, external-dns, etcd-operator

[arm4b]

I hadn't chance to really try Helm 3.0 yet, so google is your better friend than me here.

However looks like the first big visible difference between v2 and v3 is that requirements should be moved to Chart.yml instead of requirements.yml file.

[rahulparihar270992]

Hi @armab, I installed rabbitmq-ha-1.36.4 first with helm 3.0 and it succeeded:

NAMESPACE NAME READY STATUS RESTARTS AGE IP
default my-rabbit-rabbitmq-ha-0 1/1 Running 1 2d8h 10.244.3.29
default my-rabbit-rabbitmq-ha-1 1/1 Running 1 2d8h 10.244.1.24
default my-rabbit-rabbitmq-ha-2 1/1 Running 1 2d8h 10.244.2.14

So does it mean this chart works in helm 3.
But if install ss ha with :
helm install stackstorm -n st2 -f values.yaml .

The error is:

manifest_sorter.go:175: info: skipping unknown hook: "crd-install"
Error: unable to build kubernetes objects from release manifest: unable to recognize "": no matches for kind "EtcdCluster" in version "etcd.database.coreos.com/v1beta2"

@wantdrink , @armab I am also facing similar issue . Have you updated helm chart for etcd-operator ?
Can you please give me some pointer here, what next step have you taken?

[wantdrink]

@rahulparihar270992 SS chart has a set of dependencies chart. Fortunately some of them already supports Helm3.
unfortunately etcd-operator as one mandatory dependency cannot be omitted and must be installed. But its chart hasn't been updated yet for Helm3.0 (version 0.10.0 in requirement).
Let me try 0.10.2 today and see if it works.

[wantdrink]

@armab Thanks, you are right.

[wantdrink]

0.10.2 can be installed with helm3. It looks like we can move forward.