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/deployments/helm/custom-helm-uploads.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,8 +77,8 @@ steps:
77
77
This pipeline references some predefined environment variables such as`GOOGLE_BUCKET_NAME`,`GOOGLE_PROJECT_ID` and`GOOGLE_CREDENTIALS`.
78
78
For this example, we created a service account with appropriate permissions in Google Cloud, and saved the credentials into`GOOGLE_CREDENTIALS` as a Codefresh Secret. <br>
79
79
For more information, see:
80
-
[Authenticating with Google services](https://cloud.google.com/storage/docs/authentication#service_accounts){:target="_blank"}. <br>
81
-
[Codefresh pipeline configuration and secrets](https://codefresh.io/docs/docs/codefresh-yaml/variables/#user-provided-variables){:target="_blank"}.
80
+
[Authenticating with Google services](https://cloud.google.com/storage/docs/authentication#service_accounts){:target="_blank"}
81
+
[Codefresh pipeline configuration and secrets]({{site.baseurl}}/pipelines/variables/#user-provided-variables)
82
82
83
83
##Example 2: Push the chart to Chart Museum
84
84
Chart Museum is a Helm repository*server* that has an HTTP API, pluggable backends, authentication, and more.
@@ -122,4 +122,4 @@ steps:
122
122
##Related articles
123
123
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
124
124
[Using a managed Helm repository]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/)
Copy file name to clipboardExpand all lines: _docs/deployments/helm/helm-charts-and-repositories.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
-
title:"Using externalHelmrepos in Codefresh pipelines"
3
-
description:"Use external HelmCharts and repositories in Codefresh pipelines"
2
+
title:"Helmcharts and repositories"
3
+
description:"Use external Helmcharts and repositories in Codefresh pipelines"
4
4
group:deployments
5
5
sub_group:helm
6
6
toc:true
@@ -13,7 +13,7 @@ It is optional to use external Helm repositories as all Codefresh accounts alrea
13
13
Easily add your own Helm charts.
14
14
By default, we show charts from the[official Helm repository](https://github.com/kubernetes/charts){:target="_blank"}.
15
15
16
-
1. In the Codefresh UI, fromtheArtifacts section in the sidebar, select[**Helm Charts**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
16
+
1. In the Codefresh UI, from Artifacts in the sidebar, select[**Helm Charts**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
17
17
1. On the top right, click**Add Existing Helm Repository**.
18
18
You are taken to Pipeline Integrations.
19
19
1. In the Integrations page, click**Add Helm Repository**, and then select the type of Helm repo to add from the list.
@@ -66,11 +66,11 @@ Install a chart from a Helm repository to your cluster.
66
66
* Variables available for custom pipelines:
67
67
If you select a custom pipeline, the following variables are available:
68
68
*`CF_HELM_RELEASE` - name of release
69
-
*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))
69
+
*`CF_HELM_KUBE_CONTEXT` - kubectl context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/#work-with-your-services))
70
70
*`CF_HELM_INSTALLATION_NAMESPACE` - desired namespace for the release
*`CF_HELM_CHART_REPO_URL` - URL of Chart repository
@@ -79,10 +79,10 @@ Install a chart from a Helm repository to your cluster.
79
79
<br />
80
80
81
81
**Before you begin**
82
-
* Make suretht you have a Kubernetes integration with the cluster and namespace, as described[here]({{site.baseurl}}/docs/deploy-to-kubernetes/add-kubernetes-cluster/)
82
+
* Make surethat you have a Kubernetes integration with the cluster and namespace, as described[here]({{site.baseurl}}/docs//integrations/kubernetes/#connect-a-kubernetes-cluster)
83
83
84
84
**How to**
85
-
1. In the Codefresh UI, fromtheArtifacts section in the sidebar, select[**Helm Charts**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
85
+
1. In the Codefresh UI, from Artifacts in the sidebar, select[**Helm Charts**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
86
86
1. In the row with the chart to install, click**Install**.
87
87
1. Enter the**Release name** for the chart, and select the**Chart version** to install.
88
88
1. From Cluster Information, select a Kubernetes**Cluster** and the**Namespace** to install to.
@@ -105,7 +105,7 @@ You can also install Helm releases from [any Helm environment board]({{site.base
105
105
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
Copy file name to clipboardExpand all lines: _docs/deployments/helm/helm-environment-promotion.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ group: deployments
6
6
sub_group:helm
7
7
toc:true
8
8
---
9
-
Apart from the[Helm Releases]({{site.baseurl}}/docs/deployments/helm/helm-releases-management) thatshow your Kubernetes clusters at the application level, Codefresh also comes with a special environment board that allows you to track one or more applications as they move within your infrastructure (example, Dev, QA, Prod).
9
+
Apart from the[Helm Releases]({{site.baseurl}}/docs/deployments/helm/helm-releases-management)dashbaordthatshows your Kubernetes clusters at the application level, Codefresh also comes with a special environment board that allows you to track one or more applications as they move within your infrastructure (example, Dev, QA, Prod).
10
10
11
11
The environment board can function both as an overview of the whole lifecycle of the application, as well as a tool to shift-left/right Helm releases between environments.
12
12
@@ -59,7 +59,7 @@ Once you have your columns in place, you can move Helm releases between clusters
59
59
60
60
Create your own Helm board with a single or multiple Helm applications. You can create as many boards as you want.
61
61
62
-
1. In the Codefresh UI, fromtheDevOps Insights section in the sidebar, select[**Helm Boards**](https://g.codefresh.io/helm/helm-kanban/){:target="\_blank"}.
62
+
1. In the Codefresh UI, from DevOps Insights in the sidebar, select[**Helm Boards**](https://g.codefresh.io/helm/helm-kanban/){:target="\_blank"}.
By default Codefresh will use a built-in install/upgrade pipeline for performing the promotion. You can choose your own pipeline from the promotion dialog. That pipeline will be automatically provided with the following[environment variables]({{site.baseurl}}/docs/deployments/helm/helm-releases-management/#overriding-the-default-helm-actions):
182
+
By default Codefresh will use a built-in install/upgrade pipeline for performing the promotion. You can choose your own pipeline from the promotion dialog. That pipeline will be automatically provided with the following[environment variables]({{site.baseurl}}/docs/deployments/helm/helm-releases-management/#environment-variables-for-custom-helm-commands):
183
183
184
184
*`CF_HELM_RELEASE` - name of release
185
-
*`CF_HELM_KUBE_CONTEXT` -`kubectl` context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/manage-kubernetes/#work-with-your-services))
185
+
*`CF_HELM_KUBE_CONTEXT` -`kubectl` context name of target cluster (cluster name from[dashboard]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/#work-with-your-services))
186
186
*`CF_HELM_NAMESPACE` - Tiller Namespace if you use Helm 2
187
187
*`CF_HELM_INSTALLATION_NAMESPACE` - namespace where release is promoted to
*`CF_HELM_SET` - Additional values there were overriden
191
191
*`CF_HELM_CHART_JSON_GZIP` - Gzipped JSON of Helm chart (only for Helm 3)
@@ -197,7 +197,7 @@ By default Codefresh will use a built-in install/upgrade pipeline for performing
197
197
198
198
Note that the variable`CF_HELM_CHART_JSON_GZIP` is both compressed and base64 encoded. To get the raw value you need a command like`echo $CF_HELM_CHART_JSON_GZIP | base64 -d | gunzip`
199
199
200
-
>Overriding the default pipeline can only be done by[Codefresh admin users]({{site.baseurl}}/docs/administration/access-control/#users-and-administrators).
200
+
>Overriding the default pipeline can only be done by[Codefresh admin users]({{site.baseurl}}/docs/administration/account-user-management/access-control/#users-and-administrators).
201
201
202
202
Once you click the*update* button, a new build will run that will perform the deployment.
203
203
@@ -285,6 +285,6 @@ The filters are especially helpful in Helm boards with large numbers of environm
285
285
286
286
##Related articles
287
287
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
288
-
[Using external Helml repos in Codefresh pipelines]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/#add-helm-repository)
288
+
[Helm charts and repositories]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/#add-helm-repository)
Copy file name to clipboardExpand all lines: _docs/deployments/helm/helm-releases-management.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,16 +11,16 @@ toc: true
11
11
Codefresh has built-in integration for Helm that provides a unique view into your production Kubernetes cluster.
12
12
In Helm Releases, you can see the current status of your cluster, including the currently deployed releases, their previous revisions including change tracking, and even roll back to a previous release.
13
13
14
-
Codefresh also offers[an environment view for Helm releases]({{site.baseurl}}/docs/deploy-to-kubernetes/environment-dashboard/) as well as[a promotion dashboard]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion).
14
+
Codefresh also offers[an environment view for Helm releases]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/) as well as[a promotion dashboard]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion).
15
15
16
16
17
17
##View Helm releases and release information
18
18
19
19
View all the Helm releases in your cluster, and drill down into a specific release to see its services, deployed versions, manifests and more.
20
20
21
-
>Make sure you have[connected your Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/adding-non-gke-kubernetes-cluster/) to Codefresh.
21
+
>Make sure you have[connected your Kubernetes cluster]({{site.baseurl}}/docs/integrations/kubernetes/#connect-a-kubernetes-cluster) to Codefresh.
22
22
23
-
1. In the Codefresh UI, fromtheDevOps Insights section in the sidebar, select[**Helm Releases**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
23
+
1. In the Codefresh UI, from DevOps Insights in the sidebar, select[**Helm Releases**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
24
24
25
25
{% include
26
26
image.html
@@ -143,9 +143,9 @@ max-width="70%"
143
143
144
144
You can set this message for your Helm release in three ways:
145
145
146
-
1. When you manually install a Helm release from the[Helm charts screen]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/#install-chart-from-your-helm-repository), there is a field for this message.
146
+
1. When you manually install a Helm release from the[Helm charts screen]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/#install-a-chart-from-your-helm-repository), there is a field for this message.
147
147
1. Set the property`commit_message` inside the[notes.txt](https://helm.sh/docs/chart_template_guide/notes_files/){:target="\_blank"} file of your chart.
148
-
1. By providing an environment variable called`COMMIT_MESSAGE` within your[pipelineHelm step]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
148
+
1. By providing an environment variable called`COMMIT_MESSAGE` within your[Helm pipeline step]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
149
149
150
150
151
151
##Roll back a Helm release
@@ -165,20 +165,20 @@ caption="Rolling back to a previous release"
165
165
max-width="50%"
166
166
%}
167
167
168
-
>It takes time to complete rollback for a release, and the change in the cluster is not instantly updated in the Codefresh UI. If you also use a[custom rollback pipeline](#overriding-the-default-helm-actions), the delay between the cluster update and the UI refresh is even longer.
168
+
>It takes time to complete rollback for a release, and the change in the cluster is not instantly updated in the Codefresh UI. If you also use a[custom rollback pipeline](#overriding-default-helm-actions-for-releases), the delay between the cluster update and the UI refresh is even longer.
169
169
170
170
##Helm UI actions
171
171
172
172
From the main release screen, you have some additional actions.
173
173
174
-
You can issue a[Helm test](https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md) by clicking on the 'Run Test' button on the desired chart row.
174
+
You can issue aHelm test<!---[Helm test](https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md)--> by clicking on the 'Run Test' button on the desired chart row.
175
175
176
176
You can delete a release by clicking on the 'Delete' button on the desired chart row.
177
-
For deletion options, see the[helm delete documentation](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_delete.md){:target="\_blank"}, for example,*purge* will remove the revision from the release history.
177
+
<!---For deletion options, see the [helm delete documentation](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_delete.md){:target="\_blank"}, for example, *purge* will remove the revision from the release history.-->
178
178
179
179
##Helm deployment badge<!--how to add badge ask where is the badge icon-->
180
180
181
-
Similar to a[build badge]({{site.baseurl}}/docs/pipelines/build-status/#using-the-build-badge), you can also get a deployment badge for a Helm release.
181
+
Similar to a[build badge]({{site.baseurl}}/docs/pipelines/configuration/build-status/#using-the-build-badge), you can also get a deployment badge for a Helm release.
182
182
183
183
1. In the Codefresh UI, from the DevOps Insights section in the sidebar, select[**Helm Releases**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
184
184
1. In the row with the Helm release for which to add a deployment badge, click the**Settings** (gear) icon.
@@ -208,7 +208,7 @@ By default, when you take an action in the UI, Codefresh executes the native Hel
208
208
209
209
You can override these actions for a specific Helm release by defining custom pipelines for each action. This way you can add your extra logic on top of these actions. For example your own Helm uninstall pipeline might also have a notification step that posts a message to a Slack channel after a release is removed.
210
210
211
-
>Only[Codefresh admin users]({{site.baseurl}}/docs/administration/access-control/#users-and-administrators) can override the default pipelines defined for a Helm release.
211
+
>Only[Codefresh admin users]({{site.baseurl}}/docs/administration/account-user-management/access-control/#users-and-administrators) can override the default pipelines defined for a Helm release.
212
212
213
213
1. In the Codefresh UI, from the DevOps Insights section in the sidebar, select[**Helm Releases**](https://g.codefresh.io/helm/releases/releasesNew/){:target="\_blank"}.
214
214
1. In the row with the Helm release for which to override default actions, click the**Settings** (gear) icon.
@@ -227,7 +227,7 @@ max-width="50%"
227
227
1. Select the pipeline to use for the respective actions.
228
228
229
229
###Environment variables for custom Helm commands
230
-
If you do override any of these actions, the following[environment variables]({{site.baseurl}}/docs/codefresh-yaml/variables/) are available in the respective pipeline, so that you can use your own custom Helm command.
230
+
If you do override any of these actions, the following[environment variables]({{site.baseurl}}/docs/pipelines/variables/) are available in the respective pipeline, so that you can use your own custom Helm command.
231
231
232
232
**Helm Test pipeline**
233
233
*`CF_HELM_RELEASE`: Name of release
@@ -259,5 +259,5 @@ If you do override any of these actions, the following [environment variables]({
259
259
##Related articles
260
260
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
261
261
[Helm charts and repositories]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/)
Replace values in`<>` with your own (also removing`<>` in the process).
131
131
132
-
Generate an api key from[https://g.codefresh.io/user/settings](https://g.codefresh.io/user/settings) as explained in the[API page]({{site.baseurl}}/docs/integrations/codefresh-api/).
132
+
Generate an API key from the Codefresh UI:
133
+
* From your avatar dropdown, select[**User Settings**](https://g.codefresh.io/user/settings){:target="\_blank"}. See[Codefresh API integration]({{site.baseurl}}/docs/integrations/codefresh-api/).
133
134
134
135
##Related articles
135
136
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)