Add an HTTP Helm repository connector
Documentation for the provisioning of HTTP Helm Repository connectors.
You connect Harness to an HTTP Helm repository using a Harness HTTP Helm connector. This connector allows you to pull Helm charts from your repository for use as manifests in Harness pipelines.
This topic shows you how to add an HTTP Helm connector to Harness.
What you will learn from this topic
How to add an HTTP Helm connector to a Harness project so you can pull Helm charts in a pipeline.
Add an HTTP Helm connector
You can add an HTTP Helm connector at the project, org, or account scope. This procedure covers the project scope, and the process is the same for org and account. You can also add an HTTP Helm connector directly when configuring a Helm chart manifest in a service.
Follow the interactive guide below for a step-by-step walkthrough:
Perform the following steps to add an HTTP Helm Repo connector:
Open your Harness project.
In Project Settings, select Connectors.
Click New Connector, then click HTTP Helm Repo. The HTTP Helm Repo settings appear.
Overview
In Name, enter a name for the connector. Optionally, add a description and tags. Click Continue.
Details
Enter the Helm Repository URL.
In Authentication, select one of the following options:
Username and Password: Enter the Username for the account. For Password, create a new Harness Encrypted Text secret or use an existing one.
Anonymous (no credentials required). Click Continue.
Delegates Setup
In Delegates Setup, use any delegate or enter tags for the specific delegates that you want to allow to connect to this connector. Click Save and Continue.
Test Connection
Click Finish after the connection test succeeds. The connector is listed in Connectors.
Sample YAML
The following example shows a YAML for the HTTP Helm Repo connector created in this guide.
Next steps
Artifact repository connectors: learn about the other artifact repository connectors Harness supports.
Connect to an OCI Helm registry: connect to a Helm chart repository hosted on an OCI-compliant registry instead of an HTTP server.
Deploy Helm Charts: use the Helm charts pulled by this connector as manifests in a pipeline.
Use delegate selectors: control which delegates can connect to this connector.
Add a secret manager: store connector credentials in a secret manager.
Last updated
Was this helpful?