Add Helm Repository Artifact Servers

Updated 2 weeks ago by Chakravarthy Tenneti

You can add a Helm Chart Repository as an Artifact Server and then use it in Harness Kubernetes and Helm Services. See Kubernetes Deployments and Helm Deployments.

A Helm chart repository is an HTTP server that houses an index.yaml file and, if needed, packaged charts. For details, see The Chart Repository Guide from Helm.

From Helm:

Note: For Helm 2.0.0, chart repositories do not have any intrinsic authentication. There is an issue tracking progress in GitHub.
Because a chart repository can be any HTTP server that can serve YAML and tar files and can answer GET requests, you have a plethora of options when it comes down to hosting your own chart repository. For example, you can use a Google Cloud Storage (GCS) bucket, Amazon S3 bucket, Github Pages, or even create your own web server.

In this topic:

Before You Begin

Visual Summary

Here's an example of Helm Repository Artifact Source configuration.

The Helm Repository dialog has the following fields.

Step 1: Select Helm Repository

To connect to an artifact server, do the following:

  1. Click Setup.
  2. Click Connectors.
  3. Click Artifact Servers.
  4. Click Add Artifact Server.
  5. In Type, click Helm Repository.

Step 2: Display Name

This is the name you will use to select this Artifact Server in you Kubernetes and Helm Services.

Step 3: Hosting Platform

The type of server where the repo is hosted.

Step 4: Repository URL

The URL of the chart repo.

Step 5: Username and Password

If the charts are backed by HTTP basic authentication, you can also supply the username and password. See Share your charts with others from Helm.

For Amazon S3 and GCS, the Base Path setting has moved to the Harness Service Chart Specification settings.

For secrets and other sensitive settings, select or create a new Harness Encrypted Text secret.

Usage Scope is determined by the secret you selected.

Click Submit.

Next Steps

How did we do?