Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commita027c10

Browse files
committed
Update helm deployment topics
1 parentde27117 commita027c10

File tree

7 files changed

+54
-51
lines changed

7 files changed

+54
-51
lines changed

‎_data/nav.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -334,7 +334,7 @@
334334
url:"/managed-helm-repository"
335335
-title:Helm Charts and repositories
336336
url:"/helm-charts-and-repositories"
337-
-title:CustomHelmuploads
337+
-title:Creating and uploadingHelmpackages
338338
url:"/custom-helm-uploads"
339339
-title:Promoting Helm environments
340340
url:"/helm-environment-promotion"

‎_docs/deployments/helm/custom-helm-uploads.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,8 +77,8 @@ steps:
7777
This pipeline references some predefined environment variables such as`GOOGLE_BUCKET_NAME`,`GOOGLE_PROJECT_ID` and`GOOGLE_CREDENTIALS`.
7878
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>
7979
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)
8282

8383
##Example 2: Push the chart to Chart Museum
8484
Chart Museum is a Helm repository*server* that has an HTTP API, pluggable backends, authentication, and more.
@@ -122,4 +122,4 @@ steps:
122122
##Related articles
123123
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
124124
[Using a managed Helm repository]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/)
125-
[Helmenvironment promotion]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)
125+
[PromotingHelmenvironments]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)

‎_docs/deployments/helm/helm-charts-and-repositories.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
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"
44
group:deployments
55
sub_group:helm
66
toc:true
@@ -13,7 +13,7 @@ It is optional to use external Helm repositories as all Codefresh accounts alrea
1313
Easily add your own Helm charts.
1414
By default, we show charts from the[official Helm repository](https://github.com/kubernetes/charts){:target="_blank"}.
1515

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"}.
1717
1. On the top right, click**Add Existing Helm Repository**.
1818
You are taken to Pipeline Integrations.
1919
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.
6666
* Variables available for custom pipelines:
6767
If you select a custom pipeline, the following variables are available:
6868
*`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))
7070
*`CF_HELM_INSTALLATION_NAMESPACE` - desired namespace for the release
7171
*`CF_HELM_CHART_VERSION` - Chart Version,
7272
*`CF_HELM_CHART_NAME` - Chart Name
73-
*`CF_HELM_CONTEXTS` - values from[shared configuration]({{site.baseurl}}/docs/pipelines/shared-configuration/#using-shared-helm-values)
73+
*`CF_HELM_CONTEXTS` - values from[shared configuration]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/#using-shared-helm-values)
7474
*`CF_HELM_VALUES` - extra values
7575
*`CF_HELM_SET` - extra values,
7676
*`CF_HELM_CHART_REPO_URL` - URL of Chart repository
@@ -79,10 +79,10 @@ Install a chart from a Helm repository to your cluster.
7979
<br />
8080

8181
**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)
8383

8484
**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"}.
8686
1. In the row with the chart to install, click**Install**.
8787
1. Enter the**Release name** for the chart, and select the**Chart version** to install.
8888
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
105105
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
106106
[Helm integrations]({{site.baseurl}}/docs/integrations/helm/)
107107
[Helm Dashboard]({{site.baseurl}}/docs/deployments/helm/helm-releases-management)
108-
[Helm Promotion boards]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)
108+
[Promoting Hlem environments]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)
109109
[Helm best practices]({{site.baseurl}}/docs/ci-cd-guides/helm-best-practices/)
110110

111111

‎_docs/deployments/helm/helm-environment-promotion.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ group: deployments
66
sub_group:helm
77
toc:true
88
---
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).
1010

1111
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.
1212

@@ -59,7 +59,7 @@ Once you have your columns in place, you can move Helm releases between clusters
5959

6060
Create your own Helm board with a single or multiple Helm applications. You can create as many boards as you want.
6161

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"}.
6363

6464
{% include
6565
image.html
@@ -179,13 +179,13 @@ caption="Changing deployment values"
179179
max-width="40%"
180180
%}
181181

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/#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):
183183

184184
*`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))
186186
*`CF_HELM_NAMESPACE` - Tiller Namespace if you use Helm 2
187187
*`CF_HELM_INSTALLATION_NAMESPACE` - namespace where release is promoted to
188-
*`CF_HELM_CONTEXTS` -[shared configuration]({{site.baseurl}}/docs/configure-ci-cd-pipeline/shared-configuration) Helm contexts
188+
*`CF_HELM_CONTEXTS` -[shared configuration]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration) Helm contexts
189189
*`CF_HELM_VALUES` - Helm chart values
190190
*`CF_HELM_SET` - Additional values there were overriden
191191
*`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
197197

198198
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`
199199

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).
201201
202202
Once you click the*update* button, a new build will run that will perform the deployment.
203203

@@ -285,6 +285,6 @@ The filters are especially helpful in Helm boards with large numbers of environm
285285

286286
##Related articles
287287
[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)
289289
[Managing Helm releases]({{site.baseurl}}/docs/deployments/helm/helm-releases-management)
290-
[Environment Dashboard]({{site.baseurl}}/docs/deploy-to-kubernetes/environment-dashboard/)
290+
[Environment Dashboard]({{site.baseurl}}/docs/deployments/kubernetes/environment-dashboard/)

‎_docs/deployments/helm/helm-releases-management.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -11,16 +11,16 @@ toc: true
1111
Codefresh has built-in integration for Helm that provides a unique view into your production Kubernetes cluster.
1212
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.
1313

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).
1515

1616

1717
##View Helm releases and release information
1818

1919
View all the Helm releases in your cluster, and drill down into a specific release to see its services, deployed versions, manifests and more.
2020

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.
2222
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"}.
2424

2525
{% include
2626
image.html
@@ -143,9 +143,9 @@ max-width="70%"
143143

144144
You can set this message for your Helm release in three ways:
145145

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.
147147
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/).
149149

150150

151151
##Roll back a Helm release
@@ -165,20 +165,20 @@ caption="Rolling back to a previous release"
165165
max-width="50%"
166166
%}
167167

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.
169169
170170
##Helm UI actions
171171

172172
From the main release screen, you have some additional actions.
173173

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.
175175

176176
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.-->
178178

179179
##Helm deployment badge<!--how to add badge ask where is the badge icon-->
180180

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.
182182

183183
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"}.
184184
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
208208

209209
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.
210210

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.
212212
213213
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"}.
214214
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%"
227227
1. Select the pipeline to use for the respective actions.
228228

229229
###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.
231231

232232
**Helm Test pipeline**
233233
*`CF_HELM_RELEASE`: Name of release
@@ -259,5 +259,5 @@ If you do override any of these actions, the following [environment variables]({
259259
##Related articles
260260
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
261261
[Helm charts and repositories]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/)
262-
[Codefresh-managed HelmRepositories]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/)
263-
[Helmpromotion boards]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)
262+
[Using amanaged Helmrepository]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/)
263+
[PromotingHelmEnvironments]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)

‎_docs/deployments/helm/managed-helm-repository.md‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -129,7 +129,8 @@ curl -X DELETE -v -H "Authorization: Bearer <api-key>" https://h.cfcr.io/api/<co
129129

130130
Replace values in`<>` with your own (also removing`<>` in the process).
131131

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/).
133134

134135
##Related articles
135136
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp