Codefresh for GitOps

GitOps and Argo CD with Codefresh

This article reviews the concepts of GitOps and Argo CD, and how Codefresh integrates with and implements both.


GitOps is a set of best practices for application/infrastructure deployment centered around the concept of using Git as the single source of truth.

You can read more about GitOps at

Git repositories are the source-control systems that declaratively describe applications and infrastructure using code. The continuous integration and continuous delivery processes synchronize these changes with live environments, making sure that the production state always matches the desired state in Git.

The entire application lifecycle is managed by Git.

The key difference is that while the traditional workflow is based on “pushing” new code changes through the pipeline to production, a GitOps workflow is a “pull” process in which new changes are submitted, and the GitOps agent detects and synchronizes them with the production environment.

Read more in our blog, What is a GitOps workflow.

Argo CD

Argo CD is “a declarative, GitOps continuous delivery tool for Kubernetes.”

Argo CD uses a Kubernetes controller to constantly monitor the state of all resources in production and compare them against the desired states set in Git. When there are changes to the desired state, the controller detects them, and works to synchronize the production configuration to the desired configuration.

Argo CD is also designed to work with Argo Rollouts, a progressive delivery tool for handling canary and blue/green deployments with robust support for most load balancers in use today.

Codefresh for GitOps & Argo CD

Where does Codefresh come into play with GitOps and Argo CD?

Codefresh is the easiest way to get started with GitOps and Argo CD. Codefresh leverages Argo components to have the entire desired state applied from Git to your Kubernetes cluster, and then reported back to Codefresh.

GitOps Runtimes

Codefresh offers two models for GitOps deployments:

  • Hosted GitOps, which is a fully-managed version of Argo CD. The runtime for Hosted GitOps is hosted on a Codefresh cluster (easy setup) and managed by Codefresh (zero maintenance overhead).
    If you already have Argo CD installations, this is the option for you. Click once to provision the hosted runtime, and start deploying applications to clusters without having to install and maintain Argo CD.

  • Hybrid GitOps, which is a customer-managed version of Argo CD. The Hybrid GitOps runtime is hosted on the customer cluster and managed by the customer.
    The Hybrid GitOps offering retains runtimes within the customer infrastructure to comply your security rewhile giving you the power of Argo CD with Codefresh’s CI and CD tools, to help achieve continuous integration and continuous delivery goals.

Review GitOps runtime architecture.
For installation, see Hosted GitOps setup and Hybrid GitOps installation.

Argo CD applications

Codefresh supports the complete lifecycle to create and deploy Argo CD applications.

You can create full-featured Argo CD applications in Form or YAML modes. Built-in validations make it easy to identify and fix errors before commit.

The application is also completely GitOps-compliant. The application manifest is generated, committed to Git, and synced to your cluster.
See Creating and Managing GitOps applications.

Once deployed, our dashboards give you enterprise-wide visibility into deployments, and key metrics. From global analytics on applications and deployments (), to failure rate and lead time for changes (DORA dashboard), to application configuration, resource, and rollout management (Applications dashboard).

DORA metrics
Monitoring applications

Codefresh & the Argo Project

Codefresh unified all 4 projects of the Argo family into a single Runtime, providing an enterprise-supported version of all projects enhanced with unique functionality.

Our users rely on the Codefresh platform to deliver software, reliably and predictably, without disruptions. To maintain that high standard, we add several weeks of testing and bug fixes to new versions of Argo before making them available within Codefresh. Typically, new versions of Argo are available within 30 days of their release.

Codefresh for CI
Codefresh for CD
Concepts in Codefresh
Introduction to Codefresh