Upgrade to Helm 3 Charts in Kubernetes Services

Updated 3 months ago by Michael Cretzman

This topic describes how to upgrade your Harness Kubernetes Service to use Helm 3 charts.

You can use Helm 3 charts in both Kubernetes and native Helm Services. For information on upgrading native Helm Services, see Upgrade Native Helm 2 Deployments to Helm 3.

What's a native Helm deployment in Harness? Harness provides Kubernetes deployments that use Helm charts without requiring Helm or Tiller be installed in your target environment. These are called Harness Kubernetes deployments. This is the recommended method. If you want to deploy to a Kubernetes cluster using Helm explicitly, you can use native Helm deployments. You simply choose Helm as the Deployment Type when you create a Harness Service.

In this topic:

Option 1: Upgrade Helm Version Number in the Harness UI

  1. In Harness, locate a Kubernetes Service that uses Helm charts, or where you plan on using Helm charts.
  2. In Manifests, click Link Remote Manifests. The Remote Manifests settings appear.
  3. In Manifest Format, Helm Chart from Helm Repository will be selected already if you are upgrading an existing Service. For steps on configuring all of these settings, see Use a Helm Repository with Kubernetes.
  4. In Helm Version, select the Helm version of your chart, such as v3.
  5. Click Submit.

You can now use Helm 3 charts.

Option 2: Upgrade Helm Version Number in YAML

  1. In Harness, locate a Service that uses Helm charts, or where you plan on using Helm charts.
  2. In your Harness Kubernetes Service, click the Configure As Code button (</>). The index.yaml for your Service contains the current Helm version used as helmVersion: V2:
    If helmVersion is not listed, do not worry. You can add it.
  3. Click Edit.
  4. Do one of the following:
  • Change helmVersion: V2 to helmVersion: V3.
  • Add helmVersion: V3.
  1. Click Save.

You can now use Helm 3 charts.

Step 2: Add Your Helm 3 Charts

You can add charts using one of the following options:

Notes

  • You do not need to add a Delegate Profile for Helm 3. Harness includes Helm 3 support in any Delegate that can connect to the target Kubernetes cluster.
  • Custom Helm binaries — Harness ships Helm binaries with all Harness Delegates. If you want the Delegate to use a specific Helm binary, do the following. In the installed Harness Delegate folder harness-delegate, open the file config-delegate.yml. For a Helm 2 binary, add helmPath. For a Helm 3 binary, add helm3Path. Next, enter the path to the binary. For example: helm3Path: /usr/local/bin/helm_3.

Next Steps


How did we do?