You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/new-helm/using-helm-in-codefresh-pipeline.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,11 +67,12 @@ You will need to connect your repository with Codefresh as described [here]({{si
67
67
68
68
###Step 4 (optional) - Import Helm configuration(s) into your pipeline definition
69
69
70
-
Once you have single or multiple Helm repositories connected to Codefresh, you can attach one or more them to the pipeline.
71
-
Do this by opening the advanced options (the gear icon) in the variables section in the right sidebar.
72
-
Then click on*Import from shared configuration* and select the Helm context or contexts to import into the pipeline:
70
+
Once you have Helm repositories connected to Codefresh, you can import one or more of them into the pipeline. This step is 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.
71
+
72
+
1. Click the**Variables** tab on the right sidebar, and then click the**Settings** (gear) icon.
73
+
1. Click**Import from shared configuration**, and select the Helm context or contexts to import into the pipeline:
73
74
* 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/).
74
-
* To import multiple contexts, select each context toadd.
75
+
* To import multiple contexts, select each context toimport.
75
76
76
77
{% include image.html
77
78
lightbox="true"
@@ -82,10 +83,9 @@ caption="Connecting a Helm repository in the pipeline"
82
83
max-width="50%"
83
84
%}
84
85
85
-
You can also click on*Add shared configuration* directly from the three dots menu for the same functionality.
86
-
This concludes the Helm setup for Codefresh. Now you can use the Helm freestyle step in the pipeline`codefresh.yml` file.
86
+
>You can also click on*Add shared configuration* directly from the three dots menu for the same functionality.
87
87
88
-
Note that this step is only needed in pipelines that actually upload/fetchHelmcharts from/to Helm repositories. If youhave a pipeline that directly installs aHelmchart fromthegit filesystem, there is no need to import a Helm configuration.
88
+
This concludes theHelmsetup for Codefresh. Now youcan use theHelmfreestyle step inthepipeline`codefresh.yml` file.
89
89
90
90
91
91
@@ -117,13 +117,13 @@ deploy:
117
117
118
118
The Helm step can operate in one of three modes:
119
119
120
-
1. install:Install the Helm chart into a Kubernetes cluster. This is the default mode if not explicitly set.
120
+
1. install:Installs the Helm chart into a Kubernetes cluster. This is the default mode, if a mode is not explicitly set.
121
121
1. push: Packages the Helm chart and pushes it to the repository.
122
122
1. authentication only: Only sets up authentication and adds the repo to the helm. This is useful if you want to write your own helm commands using the freestyle step's`commands` property, but you still want the step to handle authentication.
123
123
124
124
The operation mode is set by the `action` field, where the value can be `install`/`push`/`auth`.
125
125
126
-
For the `install` and `push` actions, ifyou have imported multiple Helm contexts into the same pipeline, you need to define the primary Helm context to use through the `primary_helm_context` argument.
126
+
Ifyou have imported multiple Helm contexts into the same pipeline, for the `install` and `push` actions you need to define the primary Helm context to use through the `primary_helm_context` argument.
127
127
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'`.
128
128
For a description of these and other arguments, see [Configuration](#configuration).
chart_name|required for install/push|Chart reference to use, adhering to Helm's lookup rules (path to chart folder, or name of packaged chart). There's no need to prefix with `/reponame` if referencing a chart in a repository, this is handled automatically. a.k.a `CHART_NAME` but `CHART_NAME` shouldn't be used anymore.
244
244
chart_repo_url|optional|Helm chart repository URL. If a [Helm repository configuration](#step-4-optional---import-the-helm-configuration-in-your-pipeline-definition) is attached to the pipeline, this setting is ignored
245
245
chart_subdir |optional | The subfolder where the chart is located in the JFrog Artifactory Helm repository.