starlingx/docs
Code Issues Proposed changes
Files
c99da8155b907fc9beded04f0ac2d4295ae1a9d1
docs/doc/source/admintasks/kubernetes/migrate-releases-from-helm-v2-to-helm-v3-9984e7aa7374.rst
Elisamara Aoki Goncalves 67bf5229ee Helm release migration from v2 to v3 (r5,dsR6) 
Revert change in procedure made in https://review.opendev.org/c/starlingx/docs/+/890494
as according to PV testing the script helmv2 config is not applicable to stx6

Change-Id: Ic63fc7df987908d8bbbb4f348981bcb33e8e162e
Signed-off-by: Elisamara Aoki Goncalves <elisamaraaoki.goncalves@windriver.com>
2023-08-09 17:34:07 +00:00

1.2 KiB
Raw Blame History

Migrate Releases from Helm v2 to Helm v3

After upgrading a cluster, end users' Helm releases are not upgraded from version 2. Run a custom script to migrate the end users' Helm releases or installs to Helm v3.

  1. Install the /helm-2to3 plugin.

    export HELM_LINTER_PLUGIN_NO_INSTALL_HOOK=true
helm plugin install /usr/local/share/helm/plugins/2to3

  2. Move the helm2 config to helm3.

    ~(keystone-admin)]$ helm 2to3 move config

  3. Choose a Helm v2 release to migrate.

    ~(keystone-admin)]$ helmv2-cli -- helm list -a

  4. Migrate a helm2 release, for example, myApplication.

    ~(keystone-admin)]$ migrate_helm_release.py myApplication

  5. Check if it migrated successfully.

    ~(keystone-admin)]$ helm list -A -a

  6. The migrated release should not appear in helm2.

    ~(keystone-admin)]$ helmv2-cli -- helm list -a