localurl:/docs/ci-cd-guides/helm-best-practices/

-title:Templating for Kubernetes

localurl:/docs/ci-cd-guides/kubernetes-templating/

-title:GitOps deployments

localurl:/docs/ci-cd-guides/gitops-deployments/

-title:Image enrichment

localurl:/docs/ci-cd-guides/image-enrichment/

-title:Creating pipelines

localurl:/docs/pipelines/pipelines/

-title:Steps in pipelines

localurl:/docs/pipelines/steps/

localurl:/docs/pipelines/steps/

-title:Variables in pipelines

localurl:/docs/pipelines/variables/

-title:Triggers in pipelines

localurl:/docs/pipelines/triggers/

-title:Annotations in pipelines

localurl:/docs/pipelines/annotations/

-title:Monitoring pipelines

localurl:/docs/pipelines/monitoring-pipelines/

-title:Advanced workflows for pipelines

url:"/helm-best-practices"

-title:Kubernetes templating

url:"/kubernetes-templating"

-title:GitOps deployments

url:"/gitops-deployments"

-title:Image enrichment

url:"/image-enrichment"

url:"/build-and-push-an-image"

-title:Build an Image with build arguments

url:"/build-an-image-with-build-arguments"

-title:Create a Docker image for PHP

url:"/php"

-title:Share data between steps

url:"/shared-volumes-between-builds"

-title:Upload/download from Google Storage buckets

url:"/uploading-or-downloading-from-gs"

-title:Compile and test a C application

url:"/c-make"

-title:Compile and test a C++ application

url:"/cpp-cmake"

-title:Compile and release a Go application

url:"/goreleaser"

-title:Call other pipelines

url:"/call-child-pipelines"

-title:Run unit tests

url:"/hosted-runtime"

-title:Hybrid GitOps Runtime

url:"/hybrid-gitops"

-title:Monitoring &managing GitOps Runtimes

-title:Managing &monitoring GitOps Runtimes

url:"/monitor-manage-runtimes"

-title:Add external clusters to GitOps Runtimes

url:"/managed-cluster"

url:"/build-step-no-such-file-or-directory"

-title:No Dockerfile found

url:"/no-dockerfile-found"

-title:Failed to create container of image

url:"/create-container-failure"

-title:Failed to tag image

url:"/could-not-tag-image"

-title:Error Code 137

url:"/paging-issues-builds-images"

-title:Deprecating personal Git integrations

url:"/personal-git-deprecation"

-title:GitOPs runtimes

-title:GitOps runtimes

url:"/runtime-issues"

-title:Terms and Privacy Policy

url:"/terms-and-privacy-policy"

pages:

description:"Create Docker images from Dockerfiles"

redirect_from:

-/docs/administration/access-control/

-/docs/docs/build-your-first-docker-image-new/

-/docs/build-your-first-docker-image-new/

group:ci-cd-guides

toc:true

Codefresh has a native module for GitOps deployments powered by Argo CD and Argo Rollouts. It also has native support for Argo Events and Argo Workflows.

* Create a[GitOps Application]({{site.baseurl}}/docs/deployments/helm/managed-helm-repository/) either from the GUI or the CLI.

*[Monitor your GitOps applications]({{site.baseurl}}/docs/deployments/helm/helm-charts-and-repositories/) and check their health status

* You can[edit/delete/rollback]({{site.baseurl}}/docs/deployments/helm/helm-releases-management/) applications while still keeping the state in Git.

* Perform[Canary releases]({{site.baseurl}}/docs/deployments/helm/helm-environment-promotion/) via the dedicated UI

* Create a[GitOps Application]({{site.baseurl}}/docs/deployments/gitops/create-application/) either from the GUI or the CLI.

*[Monitor your GitOps applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/) and check their health status

* You can[edit/delete/rollback]({{site.baseurl}}/docs/deployments/gitops/manage-application/) applications while still keeping the state in Git.

* Perform[Canary releases]({{site.baseurl}}/docs/deployments/gitops/install-argo-rollouts/) via the dedicated UI

The Tree view is designed to impart key information at a glance. Review the sections that follow for pointers to quickly get to what you need in the Tree view.

**Context menu**

Every resource has a context menu that opens on clicking the three dots on the right of the node. The options available differ according to the type of resource.

Every resource has a context menu that opens on clicking the three dots on the right of the resource. The options available differ according to the type of resource.

{% include

image.html

lightbox="true"

file="/images/applications/current-state-resource-context-menu.png"

url="/images/applications/current-state-resource-context-menu.png"

alt="Current State Tree view:Resourcecontext menu"

caption="Current State Tree view:Resourcecontext menu"

alt="Current State Tree view:Example ofcontext menu for resource"

caption="Current State Tree view:Example ofcontext menu for resource"

max-width="50%"

%}

{% include

image.html

lightbox="true"

file="/images/applications/current-state-deep-links-context-menu.png"

url="/images/applications/current-state-deep-links-context-menu.png"

alt="Current State Tree view: Example of context menu with deep link"

caption="Current State Tree view: Example of context menu with deep link"

max-width="50%"

%}

**Resource info**

Mouse over a node to see a tooltip for that resource. For detailed information, select the resource.

lightbox="true"

file="/images/applications/current-state-tree-resource-filtered.png"

url="/images/applications/current-state-tree-resource-filtered.png"

alt="Current State Tree view: Resource inventory filtered byRollouts"

caption="Current State Tree view: Resource inventory filtered byRollouts"

alt="Current State Tree view: Resource inventory filtered bySecrets"

caption="Current State Tree view: Resource inventory filtered bySecrets"

max-width="50%"

%}

View and monitor health status of the selected application's resources in the Current State tab, in Tree or List views.

Identify the health of an application resource through thecolor-coded border andtheresource-type icon (Tree view), or the textual labels at the right of the resource (List view).

Identify the health of an application resource through theicon, as described inthetable (Tree view), or the textual labels at the right of the resource (List view).

The table describes the possible health statuses for an application resource in the Tree view.

{: .table .table-bordered .table-hover}

| Healthstatus| Description| Display in Tree view|

|Healthicon| Health status| Description|

| --------------| ------------| ------------------|

|**Healthy**| Resource is functioning as required.|{::nomarkdown}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{:/}|

|**Progressing**| Resource is not healthy but can become healthy before the timeout occurs.|{::nomarkdown}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/}|

|**Suspended**| Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.|{::nomarkdown}<img src="../../../../images/icons/current-state-suspended.png" display=inline-block">{:/}|

|**Missing**| Resource is not present on the cluster.|{::nomarkdown}<img src="../../../../images/icons/current-state-missing.png" display=inline-block">{:/}|

|**Degraded**| Resource is not healthy, or a timeout occurred before it could reach a healthy status.|{::nomarkdown}<imgsrc="../../../../images/icons/current-state-degraded.png"display=inline-block/>{:/}|

|**Unknown**| Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types.| {::nomarkdown}<img src="../../../../images/icons/current-state-unknown.png" display=inline-block">{:/}|

| {::nomarkdown}<img src="../../../../images/icons/current-state-healthy.png" display=inline-block">{:/}|**Healthy**| Resource is functioning as required.|

| {::nomarkdown}<img src="../../../../images/icons/current-state-progressing.png" display=inline-block">{:/}|**Progressing**| Resource is not healthy but can become healthy before the timeout occurs.|

| {::nomarkdown}<img src="../../../../images/icons/current-state-suspended.png" display=inline-block">{:/}|**Suspended**| Resource is not functioning, and is either suspended or paused. For example, Cron job or a canary rollout.|

|{::nomarkdown}<img src="../../../../images/icons/current-state-missing.png" display=inline-block">{:/}|**Missing**| Resource is not present on the cluster.|

| {::nomarkdown}<imgsrc="../../../../images/icons/current-state-degraded.png"display=inline-block/>{:/}|**Degraded**| Resource is not healthy, or a timeout occurred before it could reach a healthy status.|

|{::nomarkdown}<imgsrc="../../../../images/icons/current-state-unknown.png"display=inline-block/>{:/}|**Unknown**| Resource does not have a health status, or the health status is not tracked in Argo CD. For example,`ConfigMaps` resource types.|

See also[Argo CD's set of health checks](https://argo-cd.readthedocs.io/en/stable/operator-manual/health/){:target="\_blank"}.

Similar to the health status, the Current State also tracks the sync status of all application resources. The sync status identifies if the live state of the application resource on the cluster is synced with its desired state in Git.

Identify the sync status through the icon on the left of the resource nameand the color of the resource name(Tree view), or the textual labels at the right of the resource (List view).

Identify the sync status through the icon on the left of the resource name (Tree view), or the textual labels at the right of the resource (List view).

The table describes the possible syncstatuses for an application resource, and its representation in the Tree view.

The table describes the possible syncstates for an application resource in the Tree view.

{: .table .table-bordered .table-hover}

| Syncstate| Description|Display in Tree view|

| Syncicon| Sync state|Description|

| --------------| ----------| ----------|

|**Synced**| The live state of the resource on the cluster is identical to the desired state in Git.|{::nomarkdown}<img src="../../../../images/icons/current-state-synced.png" display=inline-block">{:/}|

|**Syncing**| The live state of the resource was not identical to the desired state, and is currently being synced.|{::nomarkdown}<imgsrc="../../../../images/icons/current-state-syncing.png"display=inline-block/>{:/}|

|**Out-of-Sync**|{::nomarkdown}The live state is not identical to the desired state.<br>To sync a resource, select the<b>Sync</b> option from the resource's context menu in Tree view.{:/}| {::nomarkdown}<img src="../../../../images/icons/current-state-out-of-sync.png" display=inline-block">{:/}|

|**Unknown**| The sync status could not be determined.| {::nomarkdown}<img src="../../../../images/icons/current-state-sync-unknown.png" display=inline-block">{:/}|

| {::nomarkdown}<img src="../../../../images/icons/current-state-synced.png" display=inline-block">{:/}|**Synced**| The live state of the resource on the cluster is identical to the desired state in Git.|

| {::nomarkdown}<imgsrc="../../../../images/icons/current-state-syncing.png"display=inline-block/>{:/}|**Syncing**| The live state of the resource was not identical to the desired state, and is currently being synced.|

|{::nomarkdown}<img src="../../../../images/icons/current-state-out-of-sync.png" display=inline-block">{:/}|**Out-of-Sync**| The live state is not identical to the desired state.<br>To sync a resource, select the**Sync** option from the resource's context menu in Tree view.|

|No icon|**Unknown**| The sync status could not be determined.|

url="/images/applications/apps-historical-deployment.png"

alt="GitOps Apps dashboard: Deployment chart"

caption="GitOps Apps dashboard: Deployment chart"

max-width="30%"

max-width="60%"

%}

The table lists the controls in the Rollout Player to manage an ongoing rollout.

{: .table .table-bordered .table-hover}

|Rollback playeroption| Description|

|Rollback playericon| Option| Description|

| --------------| ------------|

|**Rollback**| Not available currently.|

|**Resume**{::nomarkdown}<img src="../../../../images/icons/rollout-resume.png" display=inline-block"> {:/}| Resume a step that has been paused indefinitely.|

|**Skip step**{::nomarkdown}<img src="../../../../images/icons/rollout-skip-step.png" display=inline-block"> {:/}| Skip execution of current step. Such steps are marked as Skipped in the rollout visualization.|

|**Promote full rollout**{::nomarkdown}<img src="../../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/}| Skip remaining pause, traffic routing, and analysis steps, and deploy the current release.|

|{::nomarkdown}<img src="../../../../images/icons/rollout-rollback.png" display=inline-block"> {:/}|**Rollback**| Rollback rollout to the selec.|

| {::nomarkdown}<img src="../../../../images/icons/rollout-resume.png" display=inline-block"> {:/}|**Resume**| Resume a step that has been paused indefinitely.|

| {::nomarkdown}<img src="../../../../images/icons/rollout-skip-step.png" display=inline-block"> {:/}|**Skip step**| Skip execution of current step. Such steps are marked as Skipped in the rollout visualization.|

| {::nomarkdown}<img src="../../../../images/icons/rollout-promote-full.png" display=inline-block"> {:/}|**Promote full rollout**| Skip remaining pause, traffic routing, and analysis steps, and deploy the current release.|

The Git repository to be tracked for changes to the application's source code.

{::nomarkdown}<ul> <li><b>Repository URL</b>: The Git repo or the Helm package repo with the application source code, to be tracked for changes. If the Argo CD project is not the <spanstyle="font-family:var(--font-family-monospace);font-size:87.5%;color:#ad6800;background-color:#fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <ahref="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/"target="\_blank">Tracking and Deployment Strategies</a>.</li></ul> {:/}

{::nomarkdown}<ul> <li><b>Repository URL</b>: The Git repo or the Helm package repo with the application source code, to be tracked for changes. <br>If SSH is configured for the runtime, you can connect to the repo with either HTTPS or SSH. On selecting the repository, Codefresh automatically updates the URL format. See <a href="https://codefresh.io/docs/docs/installation/gitops/monitor-manage-runtimes/#configure-ssh-for-gitops-runtimes">Configure SSH for runtimes</a>.<br>If the Argo CD project is not the <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">default</span> project, make sure that the repo has the correct access roles for your application.<ul><li><b>Revision and Path</b>: Applies to Git repositories. </li><li><b>Chart</b>: Applies to Helm repositories. The name of the Helm package with all the resource definitions for the application, and the version. </li></ul>For more information, see <a href="https://argo-cd.readthedocs.io/en/stable/user-guide/tracking_strategies/" target="\_blank">Tracking and Deployment Strategies</a>.</li></ul> {:/}

{::nomarkdown}

<br>

{:/}

The project group to which the application belongs. A project is useful to enforce restrictions on permitted sources and targets for applications, and roles. If not defined, the application is automatically assigned to the`default` project, which is created automatically by Argo CD and has no restrictions.

The project group to which the application belongs. A project is useful to enforce restrictions on permitted sources and targets for applications and roles. If not defined, the application is automatically assigned to the`default` project, which is created automatically by Argo CD and has no restrictions.

For more information, see Argo CD's documentation on[Projects](https://argo-cd.readthedocs.io/en/stable/user-guide/projects/#projects){:target="\_blank"}.

<br><br>

{:/}

Manually synchronize an application to expedite Git-to-cluster sync. The sync options selected for manual sync override the sync options defined for the application.

The sync options, grouped into Revision and Additional Settings, are identical to the Sync options in the General settings when you created the application.

***All**: Sync all resources regardless of their sync state.

***Out of sync**: Sync_only_ resources that are`Out of sync`.

{::nomarkdown}

<br>

{:/}

<br><br>

Revision settings determine the behavior for the branch you select.

max-width="80%"

%}

You can see the example project at[https://github.com/codefresh-contrib/terraform-sample-app](https://github.com/codefresh-contrib/terraform-sample-app){:target="\_blank"}. The repository contains a simple Terraform definition that creates a VM on Google cloud.