GitOps Runtimes
Create and deploy Argo CD applications with GitOps Runtimes
The Codefresh GitOps module requires you to install GitOps Runtimes.
GitOps Runtimes are available as hosted Runtimes with Argo CD installed in the Codefresh cluster, and hybrid Runtimes with Argo CD installed in the customer’s cluster. Review the comparison between both Runtime modes.
Hosted GitOps
The SaaS version of GitOps, Hosted GitOps has Argo CD installed in the Codefresh cluster.
Hosted GitOps Runtime is installed and provisioned in a Codefresh cluster, and managed by Codefresh.
Hosted environments are full-cloud environments, where all updates and improvements are managed by Codefresh, with zero-maintenance overhead for you as the customer.
Currently, you can add one Hosted GitOps Runtime per account.
For the architecture, see Hosted GitOps Runtime architecture.
For more information on how to set up the hosted environment, including provisioning hosted runtimes, see Set up Hosted GitOps.
Hybrid GitOps
The hybrid version of GitOps, has Argo CD installed in the customer’s cluster.
Hybrid GitOps is installed in the customer’s cluster, and managed by the customer.
The Hybrid GitOps Runtime is optimal for organizations with security constraints, wanting to manage CI/CD operations within their premises. Hybrid GitOps strikes the perfect balance between security, flexibility, and ease of use. Codefresh maintains and manages most aspects of the platform, apart from installing and upgrading Hybrid GitOps Runtimes which are managed by the customer.
For more information on Hybrid GitOps, see Hybrid GitOps Runtime requirements and Hybrid GitOps Runtime installation.
Hosted vs.Hybrid GitOps
The table below highlights the main differences between Hosted and Hybrid GitOps.
| GitOps Functionality | Feature | Hosted | Hybrid |
|---|---|---|---|
| Runtime | Installation | Provisioned by Codefresh | Provisioned by customer |
| Runtime cluster | Managed by Codefresh | Managed by customer | |
| Number per account | One Runtime | Multiple Runtimes, one per cluster | |
| External cluster | Managed by customer | Managed by customer | |
| Upgrade | Managed by Codefresh | Managed by customer | |
| Uninstall | Managed by customer | Managed by customer | |
| Argo CD | Codefresh cluster | Customer cluster | |
| CI Ops | Delivery Pipelines | Not supported | Supported |
| Workflows | Not supported | Supported | |
| Workflow Templates | Not supported | Supported | |
| CD Ops | Applications | Supported: see below for details | Supported: see below for details |
| Deployment supported only on managed clusters | Deployment supported on both in-cluster and managed clusters | ||
| Self-healing interval: 90 seconds See Argo CD automatic self-healing |
Self-healing interval: 5 seconds (Argo CD default) See Argo CD automatic self-healing |
||
| Image enrichment | Supported | Supported | |
| Rollouts | Supported | Supported | |
| Integrations | Supported | Supported | |
| Dashboards | Home | Hosted Runtime and deployments | Runtimes, deployments, Delivery Pipelines |
| DORA metrics | Supported | Supported | |
| Applications | Supported | Supported |
Related articles
Codefresh Runner for pipelines
Codefresh pricing
Codefresh features