Even though GitOps is not specific to Kubernetes, current GitOps tools work great with Kubernetes in the form of cluster controllers. The GitOps controller monitors the state of the Git repository, and when there is a commit, instructs the cluster to match the same state.

Codefresh has native support for GitOps, from creatingGitOpsapplications, deploying them, andmonitoring and managing the deployments with dedicated dashboardsoptimized for GitOps.

Codefresh has native support for GitOps, from creatingArgo CDapplications, deploying,monitoring, and managingthem viatheGitOps paradigm, anddeployments with dedicated dashboardscompai GitOps.

{% include

image.html

* Connecting Argo CD and Codefresh

* Creating a CI pipeline for GitOps

* Creating an Argo CD application for GitOps

* Deploying the application

* Working with the GitOps Apps dashboard, anda look at the insights from theGitOps Dashboard (Home) and DORA dashboards

* Deploying theArgo CDapplication

* Working with the GitOps Apps dashboard, and GitOps Dashboard (Home) and DORA dashboards for additional insights

The repository with the application code contains the source code plus a Dockerfile. You can use any Git workflow for this repository. We will create a pipeline in Codefresh that creates a container image on each commit.

* For the Kubernetes configuration, the[https://github.com/codefresh-contrib/gitops-kubernetes-configuration](https://github.com/codefresh-contrib/gitops-kubernetes-configuration){:target="\_blank"} repository.

The configuration repository holds the kubernetes manifests. This is one of the critical points of GitOps:

The configuration repository holds the Kubernetes manifests.

This is one of the critical points of GitOps:

* The configuration repository holds the manifests that are also present in the Kubernetes cluster

* Whenever there is a commit to the configuration repository, the cluster is notified to deploy the new version of the files (we will set up a pipeline for this)

* Every subsequent configuration change should become a Git commit. Ad-hoc changes to the cluster with`kubectl` commands are**NOT** allowed

**Fork repositories**

* Before continuing, if don't have already your own example application, fork all three repositories into your own GitHub account.

* Before continuing, ifyoudon't have your own example application, fork all three repositories into your own GitHub account.

[Hosted GitOps runtime]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/)

[Hybrid GitOps runtime]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/)

If you don't have aruntime installed already, for this guide, install the Hosted GitOps runtime.

If you don't have aGitOps Runtime installed already, for this guide, install the Hosted GitOps runtime.

Creating a CI pipeline for GitOps is no different from creating a standard pipeline. The only difference is that as the final action for the pipeline, you should add the report image action provided by Codefresh. The report image action correlates the Docker image with the Git repository details, Jira issues associated with it, and additional information from the registry that stores the image.

Follow these steps to create a CI pipeline for GitOps:

1. Set up Jira and registry integrations for GitOps

You need to connect Jira and your container registry to Codefresh. These integrations are specific to GitOps, and differ from the pipeline integrations that you may have already set up.

Once you set up the GitOps integrations, you can reference them in the CI pipeline's report image step for Codefresh to retrieve the necessary information.

1. Set up Codefresh pipeline integration for GitOps

1. Create your Codefresh pipeline as you usually do, using the Example CI pipeline for GitOps as a guide:

1. Set up[issue-tracking and container registry integrations for GitOps](#set-up-jira-and-docker-hub-integrations-for-gitops-image-enrichment)

You need to connect Jira and your container registry to Codefresh.

These integrations are specific to GitOps, and differ from the Jira and container registry integrations that you may have already set up for pipelines.

Once you set up the GitOps integrations for Jira and container registries, you can reference them in the CI pipeline's report image step for Codefresh to retrieve the necessary information.

1. Set up[Codefresh pipeline integration for GitOps](#set-up-codefresh-pipeline-integration-for-gitops)

1. Create your Codefresh pipeline as you usually do, using the[Example CI pipeline for GitOps] as a guide:

Use existing CI actions for compiling code, running unit tests, security scanning etc.

1. Place the final action in the pipeline as the “report image” action provided by Codefresh.

See Codefresh report image

1. When the pipeline completes execution, Codefresh retrieves the information on the image that was built and its metadata through the integration names specified.

1. View the enriched image in Codefresh’s Images dashboard, and in any application in which it is used.

Below is an example of a CI pipeline for GitOps.

The pipeline:

*[Packages your Docker images]({{site.baseurl}}/docs/ci-cd-guides/building-docker-images/)

* Runs[tests]({{site.baseurl}}/docs/testing/unit-tests/)

* Performs[security scans]({{site.baseurl}}/docs/testing/security-scanning/)

* Reports image information to Codefresh

{% highlight yaml %}

{% raw %}

version: "1.0"

stages:

- "clone"

- "build"

- "report"

steps:

clone:

title: "Cloning repository"

type: "git-clone"

repo: "${{CF_REPO_OWNER}}/${{CF_REPO_NAME}}"

revision: "${{CF_BRANCH}}"

stage: "clone"

build:

title: "Building Docker image"

type: "build"

image_name: "${{CF_REPO_OWNER}}/color"

working_directory: "${{clone}}"

tag: "${{CF_SHORT_REVISION}}"

dockerfile: "Dockerfile"

registry: docker-lr

stage: "build"

ReportImageMetadataAll:

title: Report image to Codefresh CD

type: codefresh-report-image:1.0.10

working_directory: /code

stage: "report"

arguments:

CF_API_KEY: '${{CF_API_KEY}}'

CF_IMAGE: 'docker.io/${{CF_REPO_OWNER}}/color:${{CF_SHORT_REVISION}}'

CF_CONTAINER_REGISTRY_INTEGRATION: docker

CF_RUNTIME_NAME: "codefresh-hosted"

CF_GITHUB_TOKEN: '${{GITHUB_TOKEN}}'

CF_GIT_PROVIDER: github

CF_GIT_REPO: '${{CF_REPO_OWNER}}/${{CF_REPO_NAME}}'

CF_GIT_BRANCH: '${{CF_BRANCH}}'

CF_ISSUE_TRACKING_INTEGRATION: jira

CF_JIRA_MESSAGE: "${{CF_COMMIT_MESSAGE}}"

CF_JIRA_PROJECT_PREFIX: CR

{% endraw %}

{% endhighlight yaml %}

1. View the enriched image in Codefresh’s[Images dashboard]({{site.baseurl}}/docs/dashboards/images/), and in any application in which it is used.

Pipeline steps:

1.[Git-clone step]({{site.baseurl}}/docs/pipelines/steps/git-clone/): Checks out the source code of an application

1.[Build step]({{site.baseurl}}/docs/pipelines/steps/build/): Builds a Docker image

1.`codefresh-report-image`: Reports the Jira and registry information to Codefresh. Populates the values of the Codefresh Git variables from those you defined in the respective GitOps integrations.

You can see the associated metadata in the[Images dashboard](https://g.codefresh.io/images/){:target="\_blank"}.

Below is an example of a CI pipeline for GitOps.

The pipeline:

*[Packages your Docker images]({{site.baseurl}}/docs/ci-cd-guides/building-docker-images/)

* Runs[tests]({{site.baseurl}}/docs/testing/unit-tests/)

* Performs[security scans]({{site.baseurl}}/docs/testing/security-scanning/)

* Reports image information to Codefresh

{% highlight yaml %}

{% raw %}

version: "1.0"

stages:

- "clone"

- "build"

- "report"

steps:

clone:

title: "Cloning repository"

type: "git-clone"

repo: "${{CF_REPO_OWNER}}/${{CF_REPO_NAME}}"

revision: "${{CF_BRANCH}}"

stage: "clone"

build:

title: "Building Docker image"

type: "build"

image_name: "${{CF_REPO_OWNER}}/color"

working_directory: "${{clone}}"

tag: "${{CF_SHORT_REVISION}}"

dockerfile: "Dockerfile"

registry: docker-lr

stage: "build"

ReportImageMetadataAll:

title: Report image to Codefresh CD

type: codefresh-report-image:1.0.10

working_directory: /code

stage: "report"

arguments:

CF_API_KEY: '${{CF_API_KEY}}'

CF_IMAGE: 'docker.io/${{CF_REPO_OWNER}}/color:${{CF_SHORT_REVISION}}'

CF_CONTAINER_REGISTRY_INTEGRATION: docker

CF_RUNTIME_NAME: "codefresh-hosted"

CF_GITHUB_TOKEN: '${{GITHUB_TOKEN}}'

CF_GIT_PROVIDER: github

CF_GIT_REPO: '${{CF_REPO_OWNER}}/${{CF_REPO_NAME}}'

CF_GIT_BRANCH: '${{CF_BRANCH}}'

CF_ISSUE_TRACKING_INTEGRATION: jira

CF_JIRA_MESSAGE: "${{CF_COMMIT_MESSAGE}}"

CF_JIRA_PROJECT_PREFIX: CR

{% endraw %}

{% endhighlight yaml %}

Pipeline steps:

1.[Git-clone step]({{site.baseurl}}/docs/pipelines/steps/git-clone/): Checks out the source code of an application

1.[Build step]({{site.baseurl}}/docs/pipelines/steps/build/): Builds a Docker image

1.`codefresh-report-image`: Reports the Jira and registry information to Codefresh. Populates the values of the Codefresh Git variables from those you defined in the respective GitOps integrations.

Codefresh provides an easy-to-use editor to create GitOps-compatible Argo CD applications.

When creating the application, you can use the Form mode or the YAML editor, and toggle between the two.

When creating the application, you can use the Form mode or the YAML editor, andalwaystoggle between the two.

A GitOpsapplication includes:

An Argo CDapplication in Codefresh includes:

* Application definitions

Application definitions include the name, runtime, and the location of the YAML manifest. You can define subfolders by adding / to the path.

title:"GitOps imageenrichment with integrations"

title:"Imageenrichment with integrations for GitOps"

description:""

group:gitops-integrations

redirect_from: