Skip to content

Latest commit

 

History

History
68 lines (47 loc) · 3.35 KB

helm.md

File metadata and controls

68 lines (47 loc) · 3.35 KB
Raw

Helm

Setting up Helm v3

Migration from Helm v2 to v3

In order to migrate from Helm v2 to v3 all deployments need to be migrated to their respective namespaces. This can be done with the helm-2to3 plugin:

This post from Helm explains how to set up helm v3 and how to migrate your config and the Helm v2 releases:

How to migrate from Helm v2 to v3

  1. Migrate the releases from Helm2 to Helm3: This can be done per namespace (remove dry-run to do it):

    NAMESPACE=<example>
for RELEASE in $(helm list --namespace $NAMESPACE | awk '{ print $1 }' | grep -v NAME); do helm3 2to3 convert $RELEASE --delete-v2-releases --dry-run; done

    or per deployment (remove dry-run to do it):

    helm3 2to3 convert <example> --delete-v2-releases --dry-run

    after that verify that all deployments are migrated to helm v3 and removed from helm v2:

    helm2 list | grep <example>
helm3 list -A | grep <example>

  2. Patch your CICD integration Now is a good moment to upgrade helm in your ci/cd system. If you are using Concourse: you can use this guide.

  3. Test your deployments Test your deployment with Helm v3 to see if the chart works as expected:

    helm upgrade --install <example> ./charts/<example> --namespace <environment> --values ./charts/<example>_values.staging.yaml

Breaking changes

Helm v2 charts are mostly compatible with version 3. There are however some things you need to be aware of:

  • Tiller is removed Once the migration of all the deployments is done we will remove Tiller from our clusters.
  • The way CRDs are handled by Helm has changed The way Helm 3 handles CRDs has been changed. They are now treated as special resources and are never upgraded by Helm once installed. The upgrade operation should be done by the cluster operators (admins) with extra care. Few things about this change:
  • CRDs should be put in the crds directory at the top level of chart directory.
  • The YAML files in this directory cannot be templatized like any other resources from templates directory.
  • The crd-install hook , which used to take care of installing CRD files from templates directory has been removed. If there are any files with crd-install annotation, then those are skipped by Helm.
  • Files from crds directory are applied first before rendering the chart. These are never applied again if the CRDs exist in the cluster.
  • Releases are now kept in their respective K8s Namespace With this change it is not needed anymore to add an environment parameter to your deployment. The names only need to be unique per K8s Namespace. Some of the helm commands have been updated to be more in line with other package managers.

Full helm 3 changelog