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

Commit9c3fc1a

Browse files
authored
Proj one deployments (#282)
* Port content for helm deploymentsUpdate x-refs and groups* Add Helm deployment contentPorted content for Helm deployment from Classic* Update deployment topicsAdded deployment topics for K8s helm and gitops to nav yamls, and fixed xrefs* Delete unused buckets from branch* Update k8s deployment topicsAdded renamed screenshots & updated x-refs* Update Helm deployment topicsContent and x-ref updates* Delete unused topics from proj-one-deployments branchDeleted non-branch topics for clean merge
1 parentd0e0698 commit9c3fc1a

File tree

64 files changed

+1840
-5629
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

64 files changed

+1840
-5629
lines changed

‎_docs/clients/csdp-cli.md‎

Lines changed: 0 additions & 48 deletions
This file was deleted.

‎_docs/deployment/applications-dashboard.md‎renamed to ‎_docs/deployments/gitops/applications-dashboard.md‎

Lines changed: 42 additions & 37 deletions
Large diffs are not rendered by default.

‎_docs/deployment/create-application.md‎renamed to ‎_docs/deployments/gitops/create-application.md‎

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
2-
title:"Creating applications"
2+
title:"CreatingGitOpsapplications"
33
description:""
4-
group:deployment
4+
group:deployments
5+
sub_group:gitops
56
toc:true
67
---
78

@@ -19,7 +20,7 @@ Codefresh provides all the options and functionality to create and manage Argo C
1920

2021
* Edit and delete applications
2122
Once the application is created and synced to the cluster, it is displayed in the Applications dashboard. Here, you can select an application to update the application's configuration settings, or delete it.
22-
To monitor the health and sync status, deployments, and resources for the application, see[Monitoring applications]({{site.baseurl}}/docs/deployment/applications-dashboard/).
23+
To monitor the health and sync status, deployments, and resources for the application, see[MonitoringGitOpsapplications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/).
2324

2425
###Application: Definitions
2526
Application definitions include the name, runtime, and the name of the YAML manifest. By default, the YAML manifest has the same name as that of the application.
@@ -225,7 +226,7 @@ Track the application in the [Applications dashboard](https://g.codefresh.io/2.0
225226

226227

227228
###Related articles
228-
[Monitoring applications]({{site.baseurl}})/docs/deployment/applications-dashboard)
229-
[Managing applications]({{site.baseurl}})/docs/deployment/manage-applications)
230-
[Home dashboard]({{site.baseurl}})docs/reporting/home-dashboard)
231-
[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics/)
229+
[MonitoringGitOpsapplications]({{site.baseurl}})/docs/deployments/gitops/applications-dashboard)
230+
[ManagingGitOpsapplications]({{site.baseurl}})/docs/deployments/gitops/manage-applications)
231+
[Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard)
232+
[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics/)

‎_docs/deployment/images.md‎renamed to ‎_docs/deployments/gitops/images.md‎

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
title:"Images in Codefresh"
33
description:""
4-
group:deployment
4+
group:deployments
5+
sub_group:gitops
56
toc:true
67
---
78

@@ -18,7 +19,7 @@ Complete the mandatory steps to see your Images in the Codefresh UI. Each step h
1819
1. (Mandatory) Report image information to Codefresh.
1920
See the[report-image-info](https://github.com/codefresh-io/argo-hub/blob/main/workflows/codefresh-csdp/versions/0.0.6/docs/report-image-info.md){:target="\_blank"} example.
2021

21-
>If you are using an external GitHub Actions-based pipeline, we have a new template that combines image reporting and enrichment. See[Image enrichment with integrations]({{site.baseurl}}/docs/integrations/image-enrichment-overview/).
22+
>If you are using an external GitHub Actions-based pipeline, we have a new template that combines image reporting and enrichment. See[Image enrichment with integrations]({{site.baseurl}}/docs/integrations/gitops/image-enrichment-overview/).
2223
2324
###Image views in Codefresh
2425
* In the Codefresh UI, go to[Images](https://g.codefresh.io/2.0/images){:target="\_blank"}.
@@ -111,3 +112,9 @@ Selecting **more details** for an image tag.
111112
|**3**| The Git details for this image tag, such as the Git hash, the Jira issue number, Git Pull Request, commit information, the name of the user who performed the commit.|
112113
|**4**| The workflow for the image step. Select to go to the Workflow.|
113114
|**5**| The log information for the build image step in the relevant workflow. Select to view Logs panel.|
115+
116+
##Related articles
117+
[Creating GitOps applications]({{site.baseurl}})/docs/deployments/gitops/create-application)
118+
[Managing GitOps applications]({{site.baseurl}})/docs/deployments/gitops/manage-applications)
119+
[Image enrichment with integrations]({{site.baseurl}}/integrations/image-enrichment-overview)
120+
[Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard)

‎_docs/deployment/install-argo-rollouts.md‎renamed to ‎_docs/deployments/gitops/install-argo-rollouts.md‎

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,13 @@
11
---
2-
title:"Install Argo Rollouts"
2+
title:"Progressive delivery with GitOps"
33
description:""
4-
group:deployment
4+
group:deployments
5+
sub_group:gitops
56
toc:true
67
---
78

89

9-
Install Argo Rollouts on managed clusters with a single click. With Argo Rollouts installed on your cluster, you can visualize rollout progress for deployed applications in the[Applications dashboard]({{site.baseurl}}/docs/deployment/applications-dashboard/#rollout-progress-visualization).
10+
Install Argo Rollouts on managed clusters with a single click. With Argo Rollouts installed on your cluster, you can visualize rollout progress for deployed applications in the[Applications dashboard]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/#rollout-progress-visualization).
1011
If Argo Rollouts has not been installed, an**Install Argo Rollouts** button is displayed on selecting the managed cluster.
1112

1213
1. In the Codefresh UI, go to[Runtimes](https://g.codefresh.io/2.0/account-settings/runtimes){:target="\_blank"}.
@@ -24,4 +25,4 @@ If Argo Rollouts has not been installed, an **Install Argo Rollouts** button is
2425
%}
2526

2627
###Related articles
27-
[Add external clusters to runtimes]({{site.baseurl}}/docs/runtime/managed-cluster/)
28+
[Add external clusters to runtimes]({{site.baseurl}}/docs/installation/managed-cluster/)

‎_docs/deployment/manage-application.md‎renamed to ‎_docs/deployments/gitops/manage-application.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
2-
title:"Managing applications"
2+
title:"ManagingGitOpsapplications"
33
description:""
4-
group:deployment
4+
group:deployments
5+
sub_group:gitops
56
toc:true
67
---
78

@@ -49,8 +50,8 @@ Update General or Advanced configuration settings for a deployed application thr
4950

5051
{:start="3"}
5152
1. Update the**General** or**Advanced** configuration settings as needed:
52-
[General configuration]({{site.baseurl}}/docs/deployment/create-application/#application-general-configuration-settings)
53-
[Advanced configuration]({{site.baseurl}}/docs/deployment/create-application/#application-advanced-configuration-settings)
53+
[General configuration]({{site.baseurl}}/docs/deployments/gitops/create-application/#application-general-configuration-settings)
54+
[Advanced configuration]({{site.baseurl}}/docs/deployments/gitops/create-application/#application-advanced-configuration-settings)
5455
When you change a setting, the Commit and Discard Changes buttons are displayed.
5556

5657
{% include
@@ -218,7 +219,7 @@ For example, if you made changes to `api` resources or `audit` resources, type `
218219
Delete an application from Codefresh. Deleting an application deletes the manifest from the Git repository, and then from the cluster where it is deployed. When deleted from the cluster, the application is removed from the Applications dashboard in Codefresh.
219220
220221
>**Prune resources** in the application's General settings determines the scope of the delete action.
221-
When selected, both the application and its resources are deleted. When cleared, only the application is deleted. For more information, review [Sync settings]({{site.baseurl}}/docs/deployment/create-application/#sync-settings).
222+
When selected, both the application and its resources are deleted. When cleared, only the application is deleted. For more information, review [Sync settings]({{site.baseurl}}/docs/deployments/gitops/create-application/#sync-settings).
222223
Codefresh warns you of the implication of deleting the selected application in the Delete form.
223224
224225
1. In the Codefresh UI, go to the [Applications dashboard](https://g.codefresh.io/2.0/applications-dashboard/list){:target="\_blank"}.
@@ -351,10 +352,9 @@ The table describes the options for the `Rollout` resource.
351352

352353

353354
###Related articles
354-
[Creating applications]({{site.baseurl}}/docs/deployment/create-application)
355+
[CreatingGitOpsapplications]({{site.baseurl}}/docs/deployments/gitops/create-application)
355356
[Home dashboard]({{site.baseurl}}/docs/reporting/home-dashboard)
356-
[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics)
357-
357+
[DORA metrics]({{site.baseurl}}/docs/reporting/dora-metrics)
358358

359359

360360

Lines changed: 125 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,125 @@
1+
---
2+
title:"Creating and uploading Helm packages"
3+
description:"Manually create and upload Helm packages"
4+
group:deployments
5+
sub_group:helm
6+
redirect_from:
7+
-/docs/create-helm-artifacts-using-codefresh-pipeline/
8+
toc:true
9+
---
10+
11+
Helm packages are just TAR files. Helm repositories are simple file hierarchies with an extra[index.yaml](https://helm.sh/docs/developing_charts/#the-chart-repository-structure){:target="\_blank"}.
12+
You can run custom commands and manually upload indexes and packages to a Helm repo.
13+
14+
>This articles shows some non-standard Helm examples.
15+
For the basic use cases, or if you are just getting started with Helm, see our[Helm quick start guide]({{site.baseurl}}/docs/getting-started/helm-quick-start-guide/) and[Using Helm in CI pipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
16+
17+
##Package a Helm chart
18+
Below is an example of a freestyle step in a Codefresh pipeline that packages the Helm chart and then extracts the chart name from the command output. It also saves that package name in an environment variable for later use.
19+
20+
`YAML`
21+
{% highlight yaml %}
22+
{% raw %}
23+
helm_package:
24+
image: devth/helm
25+
commands:
26+
- cf_export PACKAGE=$(helm package <mychart> | cut -d " " -f 8)
27+
{% endraw %}
28+
{% endhighlight %}
29+
30+
The`helm package` command expects a path to an unpacked chart. Replace`<mychart>` in the example with the directory that holds your chart files. Note that this directory must have the same name as the chart name, as per Helm requirements.<br>
31+
See[Helm package docs](https://github.com/kubernetes/helm/blob/master/docs/helm/helm_package.md){:target="_blank"} and[Helm charts overview](https://github.com/kubernetes/helm/blob/master/docs/charts.md){:target="_blank"} for more information.
32+
33+
{{site.data.callout.callout_info}}
34+
To use`cf_export`and make the variable available to other steps in the pipeline, see [Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables).
35+
{{site.data.callout.end}}
36+
37+
##Example 1: Push the chart to GCS based Helm Repository
38+
The first example pushes the packaged chart into a public cloud storage service, like AWS S3, Azure Storage, or Google Cloud Storage. We chose Google Cloud Storage (GCS) for this example.
39+
Our pipeline has three steps:
40+
41+
{:start="1"}
42+
1. download_index: download the Helm`index.yaml` file from GCS, or create one of it's not there.
43+
44+
{:start="2"}
45+
2. helm_package_merge: package the chart as described earlier, and also merge the new package into the downloaded`index.yaml` file, using the `helm repo index --merge` command.
46+
47+
{:start="3"}
48+
3. push_gcs: upload the updated`index.yaml` file and the newly created package to GCS.
49+
50+
`YAML`
51+
{% highlight yaml %}
52+
{% raw %}
53+
steps:
54+
download_index:
55+
image: appropriate/curl:latest
56+
commands:
57+
- 'curlhttps://storage.googleapis.com/$GOOGLE_BUCKET_NAME/index.yaml --output ./index.yaml --fail || :'
58+
- '[ ! -f ./index.yaml] && echo "apiVersion: v1">./index.yaml'
59+
helm_package_merge:
60+
image: devth/helm
61+
commands:
62+
- cf_export PACKAGE=$(helm package <mychart> | cut -d " " -f 8)
63+
- helm repo index --merge ./index.yaml .
64+
push_gcs:
65+
image: camil/gsutil
66+
commands:
67+
- echo -E $GOOGLE_CREDENTIALS > /gcs-creds.json
68+
- echo -e "[Credentials]\ngs_service_key_file = /gcs-creds.json\n[GSUtil]\ndefault_project_id = $GOOGLE_PROJECT_ID" > /root/.boto
69+
- gsutil cp ./index.yaml gs://$GOOGLE_BUCKET_NAME
70+
- gsutil cp $PACKAGE gs://$GOOGLE_BUCKET_NAME
71+
{% endraw %}
72+
{% endhighlight %}
73+
74+
75+
###Environment setup
76+
77+
This pipeline references some predefined environment variables such as`GOOGLE_BUCKET_NAME`,`GOOGLE_PROJECT_ID` and`GOOGLE_CREDENTIALS`.
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+
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"}.
82+
83+
##Example 2: Push the chart to Chart Museum
84+
Chart Museum is a Helm repository*server* that has an HTTP API, pluggable backends, authentication, and more.
85+
Read more about[Chart Museum](https://github.com/kubernetes-helm/chartmuseum){:target="_blank"}.
86+
87+
In this example, we already have a Chart Museum server running, so we'll push the packaged chart to it.
88+
89+
The steps will be:
90+
91+
{:start="1"}
92+
1. helm_package: package the chart as described earlier.
93+
94+
{:start="2"}
95+
2. get_repo_url: In order to avoid hard-coding the repository URL into the pipeline, we will retrieve it from the Codefresh Helm integration.
96+
In this case, we have added our repository with Codefresh as described in[Using external Helml repos in Codefresh pipelines]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories).
97+
Replace`<reponame>` in the example with the name you gave to your repository when you added it to Codefresh.
98+
99+
{:start="3"}
100+
3. helm_push: call the Chart Museum HTTP api to just upload the package. Chart Museum will take care of the rest.
101+
102+
`YAML`
103+
{% highlight yaml %}
104+
{% raw %}
105+
steps:
106+
helm_package:
107+
image: devth/helm
108+
commands:
109+
- cf_export PACKAGE=$(helm package <mychart> | cut -d " " -f 8)
110+
get_repo_url:
111+
image: codefresh/cli:latest
112+
commands:
113+
- cf_export HELM_URL=$(codefresh get ctx <reponame> -o=yaml | grep repositoryUrl | cut -d "'" -f 2)
114+
helm_push:
115+
image: appropriate/curl
116+
commands:
117+
- curl --data-binary "@$PACKAGE" $HELM_URL/api/charts
118+
{% endraw %}
119+
{% endhighlight %}
120+
121+
122+
##Related articles
123+
[Using Helm in a Codefresh pipeline]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/)
124+
[Using a managed Helm repository]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/)
125+
[Helm environment promotion]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion)

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp