Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarified helm registry support #8310

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarified helm registry support #8310

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion docs/platform/triggers/trigger-pipelines-on-new-helm-chart.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,10 +69,15 @@ When you add the Helm chart to Harness as a manifest, you have different options

![](./static/trigger-pipelines-on-new-helm-chart-05.png)

#### OCI Helm registries are not supported with Harness triggers
#### Supported Helm registries and limitations.

You cannot use [OCI Helm Registries](../connectors/artifact-repositories/connect-to-an-artifact-repo.md) with Helm Chart triggers.

You can use:
- [HTTP Helm](/docs/platform/connectors/code-repositories/ref-source-repo-provider/http-helm-repo-connector-settings-reference)
- [S3](/docs/platform/connectors/cloud-providers/ref-cloud-providers/gcs-connector-settings-reference)
- [Google Cloud Storage](/docs/platform/connectors/cloud-providers/ref-cloud-providers/aws-connector-settings-reference)

### Create a Helm Chart trigger

Typically, you add a Helm Chart trigger to a pipeline that deploys a Helm chart. The Helm chart is added to the CD stage in the pipeline, as part of the Harness Service **Manifest**.
Expand Down
Loading