Helm2 to Helm3
Reference: https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/

Helm2 to Helm3

Upgrading Helm2 to Helm3?

As the Kubernetes version keeps evolving it is imperative to keep upgrading the software stack. If you are running Kubernetes apps helm is a given packaging/deployment tool you would use.The latest available EKS version is?1.21, From 1.17 the helm2 is no longer supported so whoever is having deployment releases in helm2 have to upgrade and there is no other choice. This is my experience with helm2 to 3 upgrade. The helm2to3 plugin is an excellent plugin/tool which comes handy to cleanup your old helm2 releases

Prerequiste

My Jumphost is an Ubuntu instance to connect to the EKS Cluster. Assuming that you have setup the Kubeconfig to point to the right EKS cluster. Before you start off run the kube config view or Kubectl get nodes to ensure you are not accidentally connected to Prod cluster?

  • Install Helm 2 version and ensure you have helm2 running verify by typing helm version (helm binary should point to helm2)
  • Install helm3 & rename binary as helm3 installable and verify by helm3 version command that you have helm-3 mapped to helm3
  • Make a list of all helm2 objects installed, Run a “helm ls -all” This lists all helm2 objects/deployments (In this scenario lets assume we have a elastic stateful set and kibana deployment listed in helm2 release)
  • Run helm3 repo list”. If you just have helm2 objects this will return empty

PlugIn Setup

  • Install the helm2to3 plugin, Refer this excellent documentation https://helm.sh/blog/migrate-from-helm-v2-to-helm-v3/.
  • Run “helm3 plugin install https://github.com/helm/helm-2to3
  • Migrate and Cleanup Helm v2 configuration and releases in-place to Helm v3.
  • Move the Helm2 config to helm3.?
  • First do the dry run “helm3 2to3 move config --dry-run”?
  • Run the actual command if dry-run goes fine “helm3 2to3 move config”
  • Run the helm repo list “helm3 repo list”. You will see the added repos?
  • Migrate Helm v2 releases (MOST IMPORTANT STEP). This will convert the specified release helm2 object to helm3 release which is cool
  • helm3 2to3 convert --dry-run elastic
  • helm3 2to3 convert --dry-run elastic
  • helm3 2to3 convert --dry-run kibana
  • helm3 2to3 convert --dry-run kibana

Cleanup and enjoy

  • Get rid of Tiller and old releases now. (NOTE: DON’T RUN THIS UNTIL YOU HAVE MIGRATED ALL HELM2 OBJECTS)
  • helm3 2to3 cleanup --dry-run
  • helm3 2to3 cleanup

Vishal Patel

Embracing Change for the Greater Good | Senior Data Quality Engineer & Seasoned IT Professional

3 年

That’s the smooth way of upgrading helm2-helm3. Nicely describe

要查看或添加评论,请登录

Mahesh E.的更多文章

  • ELK and its importance

    ELK and its importance

    The success of a software product depends on how well we can maintain, enhance, and support a product you develop…

  • Containers

    Containers

    Docker is a Container management kit allowing users to create, publish, and run image thumbprints with a variety of…

    2 条评论
  • Thoughts & Dreams

    Thoughts & Dreams

    Wavering thoughts across my mind When will you relax and when you will unwind One thought here can take a toll One…

    7 条评论
  • Stakeholder and Project

    Stakeholder and Project

    What is a Stakeholder ? The Stakeholder word is often used in a project but often it is under rated for its importance.…

    2 条评论

社区洞察

其他会员也浏览了