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/gitops/images.md
+40-11Lines changed: 40 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,22 +6,51 @@ sub_group: gitops
6
6
toc:true
7
7
---
8
8
9
-
Building Docker images is one of the most basic requirementsfor creating Codefresh pipelines and Argo Workflows.
9
+
Building Docker images is one of the most basic requirementsof Codefresh pipelines and Argo Workflows.
10
10
Once you create an image, push the image to a registry, and report it to Codefresh, image information is continually updated in the Images page.
11
11
12
-
##Requirements for Images in Codefresh
12
+
If you
13
+
14
+
##Requirements for images in
15
+
16
+
Images are pulled to the dashboard
17
+
18
+
13
19
Complete the mandatory steps to see your Images in the Codefresh UI. Each step has links to examples in the Codefresh Hub for Argo.
14
20
15
-
1. (Mandatory) Build the Docker image, and push the image to any registry.
16
-
See[Create a Docker image using Kaniko](https://codefresh.io/argohub/workflow-template/kaniko){:target="\_blank"}.
17
-
1. (Optional) Enrich image information with annotations and metadata.
18
-
For Git and Jira image enrichment examples, see[Codefresh-metadata image enrichment](https://codefresh.io/argohub/workflow-template/CSDP-metadata){:target="\_blank"}.
19
-
1. (Mandatory) Report image information to Codefresh.
20
-
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.
21
+
1. (Mandatory) Build and push the Docker image
22
+
* Codefresh pipelines
23
+
Use the`build` step to build a Docker image declaratively in simple or multi-stage Dockerfiles. See[Build step in pipelines]({{site.baseurl}}/docs/pipelines/steps/build/).
24
+
25
+
The pipeline pushes the image to the default Docker registry.
26
+
You can also push the image to any external Docker registry that you integrate with Codefresh. See[Docker Registries for pipeline integrations]({{site.baseurl}}/docs/integrations/docker-registries/).
27
+
28
+
Review different scenarios for building and pushing Docker images in our[Build/push examples]({{site.baseurl}}/docs/example-catalog/examples/#buildpush-examples).
29
+
30
+
* GitOps
31
+
Create the Docker image.
32
+
[Create a Docker image using Kaniko](https://codefresh.io/argohub/workflow-template/kaniko){:target="\_blank"}.
33
+
34
+
1. (Mandatory) GitOps: Connect to Docker registries
35
+
Connect Docker registries to Codefresh to store Docker images.
1. (Mandatory) GitOps: Report image information to Codefresh.
39
+
This is the equivalent to pushing the image in Codefresh pipelines.
40
+
Use 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"} DAG template to report image information to Codefresh.
21
41
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/).
42
+
>If you are using an external platform or tool for your CI pipelines such as GitHub Actions or Jenkins, or even Codefresh pipelines, we have a new template that combines image reporting and enrichment. See[GitOps CI integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations) for details.
43
+
44
+
1. (Optional) Enrich image with annotations and metadata
45
+
Image enrichment exposes metadata such as feature requests, pull requests, and logs as part of the application’s deployment, for visibility into all aspects of the deployment, making it easier to track actions and identify root cause of failures.
Copy file name to clipboardExpand all lines: _docs/deployments/helm/custom-helm-uploads.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ toc: true
11
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
12
You can run custom commands and manually upload indexes and packages to a Helm repo.
13
13
14
-
>Thisarticles shows some non-standard Helm examples.
14
+
>Thisarticle shows some non-standard Helm examples.
15
15
For the basic use cases, or if you are just getting started with Helm, see our[Helm quick start guide]({{site.baseurl}}/docs/quick-start/ci-quickstart/deploy-with-helm/) and[Using Helm in pipelines]({{site.baseurl}}/docs/deployments/helm/using-helm-in-codefresh-pipeline/).
16
16
17
17
##Package a Helm chart
@@ -28,7 +28,7 @@ helm_package:
28
28
{% endhighlight %}
29
29
30
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.
31
+
See[Helm package docs](https://helm.sh/docs/helm/helm_package/){:target="_blank"} and[Helm charts overview](https://helm.sh/docs/topics/charts/){:target="_blank"} for more information.
32
32
33
33
{{site.data.callout.callout_info}}
34
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).
Copy file name to clipboardExpand all lines: _docs/deployments/helm/helm-releases-management.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -171,10 +171,10 @@ max-width="50%"
171
171
172
172
From the main release screen, you have some additional actions.
173
173
174
-
You can issue a Helm test<!--- [Helm test](https://github.com/kubernetes/helm/blob/master/docs/chart_tests.md)--> by clicking onthe'Run Test' button onthe desired chart row.
175
-
176
-
You can deletea 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 removethe revision from the release history.-->
174
+
Selecttherow withthe desired chart, and:
175
+
* Issue a[Helm test](https://helm.sh/docs/topics/chart_tests/){:target="\_blank"} by clicking on the 'Run Test' button.
176
+
* Deletea release by clicking on the 'Delete' button.
177
+
For deletion options, see the[Helm delete documentation](https://helm.sh/docs/helm/helm_uninstall/){:target="\_blank"}. For example,*purge*removesthe revision from the release history.
178
178
179
179
##Helm deployment badge<!--how to add badge ask where is the badge icon-->
Copy file name to clipboardExpand all lines: _docs/deployments/kubernetes/deployment-options-to-kubernetes.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
@@ -58,11 +58,11 @@ Using this YAML example, we'll add an additional step to deploy the image in Doc
58
58
59
59
##Describe your deployment
60
60
The following instructions describe how to create a new service in your Kubernetes cluster in order to deploy to it.
61
-
<!--- >If you're deployingto an existing service in your Kubernetes cluster,please skip to the [nextstep]({{site.baseurl}}/docs/getting-started/deployment-to-kubernetes-quick-start-guide/#add-a-deployment-step).-->
61
+
>To deployto an existing service in your Kubernetes cluster,see[Add a deploymentstep](#add-a-deployment-step).
62
62
63
63
64
-
1.Go tothe**`Kubernetes`→`Services page`**.
65
-
1. Click the button**“Add Service”**.
64
+
1.In the Codefresh UI, from Ops inthesidebar, select[**KubernetesServices**](https://g.codefresh.io/kubernetes/services/){:target="\_blank"}.
Copy file name to clipboardExpand all lines: _docs/getting-started/ci-codefresh.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -121,7 +121,7 @@ See [Slack notifications in Codefresh]({{site.baseurl}}/docs/integrations/notifi
121
121
**Jira notifications**
122
122
Codefresh integrates with Jira in several ways:
123
123
The standard integration provides the highest visibility into your GitOps deployments. Referencing the integration in your pipeline pulls in all the Jira information and enriches the image with the issue-tracking information.
124
-
Our versatile[Jira Issue Manager](https://codefresh.io/steps/step/jira-issue-manager?__hstc=13221992.d6be31528e6c55e9c8e25cbf4f7ec143.1637822320970.1673765905554.1673785426249.294&__hssc=13221992.18.1673785426249&__hsfp=1203046529{:target="\_blank"} step can be used to create Jira issues, comment on existing Jira issues, change the status of an issue, and even add a description to your issue.
124
+
Our versatile[Jira Issue Manager](https://codefresh.io/steps/step/jira-issue-manager){:target="\_blank"} step can be used to create Jira issues, comment on existing Jira issues, change the status of an issue, and even add a description to your issue.
125
125
126
126
127
127
See[Jira notifications in Codefresh]({{site.baseurl}}/docs/integrations/notifications/jira-integration/) and[examples for Jira notification]({{site.baseurl}}/docs/example-catalog/ci-examples/sending-the-notification-to-jira/).
Copy file name to clipboardExpand all lines: _docs/integrations/google-marketplace.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ toc: true
6
6
---
7
7
8
8
Codefresh has partnered with[Google Cloud](https://cloud.google.com/){:target="\_blank"} and allows you to install a Codefresh pipeline builder within your own Kubernetes cluster.
9
-
The integration is available in the Google Marketplace for Kubernetes apps at[https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh](https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh){:target="\_blank"}.
9
+
The integration is available in the Google Marketplace for Kubernetes apps at[https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas](https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas){:target="\_blank"}.
10
10
11
11
Once you configure Codefresh to use your own Kubernetes cluster for builds, you can enjoy all benefits of a**hybrid** installation as the Codefresh UI and management dashboards will still run in a SAAS manner, while the actual builds and pipelines will execute in your own cluster.
12
12
@@ -24,7 +24,7 @@ To start the integration, you need the following:
24
24
1. A[GKE cluster](https://cloud.google.com/kubernetes-engine/docs/quickstart){:target="\_blank"} that will run all builds and pipelines
25
25
1. A[Codefresh account]({{site.baseurl}}/docs/administration/account-user-management/create-a-codefresh-account/) (creating an account is free, you pay only for builds)
26
26
27
-
Then visit the Codefresh GKE page at[https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh](https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh){:target="\_blank"}.
27
+
Then visit the Codefresh GKE page at[https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas](https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas){:target="\_blank"}.
28
28
29
29
##Using Codefresh from the Google Marketplace
30
30
@@ -52,7 +52,7 @@ To start using the service, you need to [enable billing](https://cloud.google.co
52
52
53
53
You will pay for the cluster resources to Google, plus the Codefresh builds. Codefresh does not collect any payment from you directly. Google Cloud will invoice you for both the cluster infrastructure and the cluster usage.
54
54
55
-
Current pricing for Codefresh builds is always shown in the[marketplace page](https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh){:target="\_blank"}.
55
+
Current pricing for Codefresh builds is always shown in the[marketplace page](https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas){:target="\_blank"}.
56
56
57
57
##Install the Google Marketplace
58
58
@@ -80,7 +80,7 @@ With the token at hand, we can go to the Google marketplace.
80
80
81
81
###Step 2: Install the Codefresh application in your Google Cloud cluster
1. From the dropdown menu at the top of the page, select a Google project that has billing enabled.
85
85
1. Click**Configure**.
86
86
@@ -233,7 +233,7 @@ caption="Removing the Codefresh application"
233
233
alt="Removing the Codefresh application"
234
234
%}
235
235
236
-
You can install the Codefresh builder again from the[marketplace](https://console.cloud.google.com/marketplace/details/codefresh-gke/codefresh){:target="\_blank"}.
236
+
You can install the Codefresh builder again from the[marketplace](https://console.cloud.google.com/marketplace/product/codefresh-gke/codefresh-saas){:target="\_blank"}.
237
237
238
238
##Related articles
239
239
[Manage your cluster]({{site.baseurl}}/docs/deployments/kubernetes/manage-kubernetes/)