This article describes how to install GitOps Runtimes in a Codefresh account using a Helm chart on a_cluster that already has an Argo CD instance_.

This option allows you to install the GitOps Runtime without deploying a new Argo CD instance. Instead, you_install the GitOps Runtime in the same namespace as the existing Argo CD instance_. The Runtime authenticates with the Argo CD instance through the[Argo CD Admin API token](({{site.baseurl}}/docs/installation/gitops/runtime-argocd-admin-api-token/)) which you need to provide, and connects to key Argo CD services.

This option allows you to install the GitOps Runtime without deploying a new Argo CD instance. Instead, you_install the GitOps Runtime in the same namespace as the existing Argo CD instance_. The Runtime authenticates with the Argo CD instance through the[Argo CD Admin API token]({{site.baseurl}}/docs/installation/gitops/runtime-argocd-admin-api-token/) which you need to provide, and connects to key Argo CD services.

The Codefresh`values.yaml` available[here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}, contains all the arguments you can configure, including optional ones.

Before installing the GitOps Runtime, ensure your environment meets the necessary system requirements, such as the Kubernetes cluster server version and minimum resource requirements needed for a smooth and successful installation.

Depending on your installation mode, you also need to complete the[prerequisites]({{site.basseurl}}/docs/installation/gitops/runtime-prerequisites/) before installing the Runtime.

Depending on your installation mode, you also need to complete the[prerequisites]({{site.baseurl}}/docs/installation/gitops/runtime-prerequisites/) before installing the Runtime.