For more details on adding extra Helm repositories see the[Helm integration page]({{site.baseurl}}/docs/integrations/helm/).

Once you have set up Helm integrations in Codefresh, you can inject single or multiple Helm repository contexts into your pipelines.

Select the**Import from shared configuration** option in the "Environment Variables" section, and then select the Helm repository or Helm repositories to inject into the pipeline.

The repository settings are injected as environment variables into the pipeline so you can use them as you wish.

Once connected, any Helm repository context can be injected into pipelines by selecting "Import from shared configuration" (under "Environment Variables" section) and selecting the name of the repository.

The repository settings will be injected as environment variables into the pipeline so you can use them as you wish.

{% include image.html

lightbox="true"

max-width="70%"

%}

If you are using the Helm step, it will use these settings to connect to your authenticated repository automatically. More info on the Codefresh Helm step can be found in the[Helm Usage Guide]({{site.baseurl}}/docs/new-helm/using-helm-in-codefresh-pipeline/).

If you are using the Helm step, the step uses the Helm repository context's settings to automatically connect to your authenticated repository.

If the pipeline has multiple Helm repository contexts, then you must specify the primary repsoitory context.

For more info on the Codefresh Helm step, see[Using Helm in Codefresh pipelines]({{site.baseurl}}/docs/new-helm/using-helm-in-codefresh-pipeline/).

toc:true

We have created a[special Helm step](https://codefresh.io/steps/step/helm) for easy integration of Helm in Codefresh pipelines. The Helm step facilitates authentication, configuration and execution of Helm commands.

We have created a[special Helm step](https://codefresh.io/steps/step/helm)for easy integration of Helm in Codefresh pipelines. The Helm step facilitates authentication, configuration and execution of Helm commands.

The example Codefresh application also comes with a[sample chart](https://github.com/codefresh-contrib/python-flask-sample-app/tree/with-helm/charts/python) that is used in the[Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/).

You can create the chart manually or by using the[helm create](https://helm.sh/docs/helm/#helm-create) command on your workstation. There are also several thirdpart tools that can create Helm packages for you such as[Draft](https://draft.sh/).

You can create the chart manually or by using the[helm create](https://helm.sh/docs/helm/#helm-create) command on your workstation. There are also several thirdparty tools that can create Helm packages for you such as[Draft](https://draft.sh/).

Once you have your Helm chart ready, commit it to the same git repository that contains the source code of your application. It should be in a folder called`charts`. Codefresh can also work with Helm charts that are in different Git repositories. We suggest however that you keep both the source code and the Helm chart of an application in the same git repository as this makes chart management much easier.

max-width="70%"

%}

If you are still using Helm 2 make sure also that your Kubernetes cluster has the server part of Helm installed (called Tiller).

any other terminal that has access to your cluster via`kubectl`. This process is not needed if you use Helm 3.

To verify that your cluster is setup for Helm select the*Helm Releases* item from the left sidebar in the Codefresh UI. You should see the[Helm releases]({{site.baseurl}}/docs/new-helm/helm-releases-management/) in your cluster or an empty screen if you just started using Helm.

You will need to connect your repository with Codefresh as described[here]({{site.baseurl}}/docs/new-helm/add-helm-repository/), or obtain your managed Helm repository URL as described[here]({{site.baseurl}}/docs/new-helm/managed-helm-repository/#chart-repository-url).

Once you have a Helm repository connected, attach it to the pipeline. Do this by opening the advanced options (the gear icon) in the variables section in the right sidebard. Then click on*Import from shared configuration* and choose the`CF_HELM_DEFAULT`[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/).

Once you have single or multiple Helm repositories connected to Codefresh, you can attach one or more them to the pipeline.

Do this by opening the advanced options (the gear icon) in the variables section in the right sidebar.

Then click on*Import from shared configuration* and select the Helm context or contexts to import into the pipeline:

* To import a single context, which is the general requirement, select the`CF_HELM_DEFAULT`[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration/).

* To import multiple contexts, select each context to add.

{% include image.html

lightbox="true"

Note that this step is only needed in pipelines that actually upload/fetch Helm charts from/to Helm repositories. If you have a pipeline that directly installs a Helm chart from the git filesystem, there is no need to import a Helm configuration.

of this limitation and will soon improve the way Codefresh works with multiple Helm configurations.

You can use the helm typed step from the[Step Marketplace](https://codefresh.io/steps/step/helm)

You can use the`helm` typed step from the[Step Marketplace](https://codefresh.io/steps/step/helm).

The Helm step can be configured using environment variables, which can be provided in any of the various ways supported by Codefresh as described[here]({{site.baseurl}}/docs/codefresh-yaml/variables/#user-provided-variables).

-'STR_WITH_COMAS="one\,two\,three"'

For the `auth` action, if the chart has dependencies on other repos, then to authenticate the referenced repos, you need to add `use_repos_for_auth_action:'true'`.

action|defaults to 'install'|Operation mode:`install`/`push`/`auth`