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.

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

Review how Codefresh[validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).

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

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

Before initiating the installation, Codefresh automatically validates the`values.yaml` file to verify that the supplied values are correct.

A validation error will automatically terminate the installation.

The Codefresh`values.yaml` located[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.

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

Review how Codefresh[validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).

To install the GitOps Runtime with an existing Argo CD instance, see[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/).

After installation, you can:

* Continue with the Configuration & Management steps in the installation wizard. See[Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).

* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.

* View the installed Runtime in the Runtimes page.

* Depending on your setup, complete the post-installation configuration:

* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).

* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).

After installation, go to**GitOps Runtimes > List View**:

%}

{% if page.collection != site.gitops_collection %}

After completing the installation, you may need to perform additional configuration depending on your setup.

* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).

* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).

{% endif %}

If you use private registries, you must override specific image values for the different subcharts and container images.

Our utility helps override image values for GitOps Runtimes by creating`values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these`values` files to override the images, as needed.

For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.

Repository certificates are required to authenticate users to on-premises Git servers.

If your Git servers are on-premises, add the repository certificates to your Codefresh`values` file, in`.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this[section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.

{% highlight yaml %}

global:

codefresh:

tls:

caCerts:

# optional - use an existing secret that contains the cert

# secretKeyRef:

# name: my-certificate-secret

# key: ca-bundle.crt

# or create "codefresh-tls-certs" secret

secret:

create: true

content: |

-----BEGIN CERTIFICATE-----

...

-----END CERTIFICATE-----

{% endhighlight yaml %}

Feel free to use a different chart version and a unique name for the Runtime.You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.

You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.

The example is valid for the tunnel-based access mode. For ingress-based or service-mesh-based access modes, add the required arguments and values, as described in[GitOps Runtimes with ingress controllers/service meshes]({{site.baseurl}}/docs/installation/gitops/runtime-install-ingress-service-mesh-access-mode/).

Depending on your configuration:

* If you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See[Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.

* If you installed the GitOps Runtime on a cluster with Argo CD, you can[migrate Community Argo CD Applications](#migrate-argo-cd-applications-to-codefresh-gitops-runtime) to GitOps applications.

Depending on your configuration, if you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See[Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.

By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add[Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use[Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and[create and deployGitOps applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).

By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add[Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use[Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and[create and deployArgo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).

{% if page.collection != site.gitops_collection %}

If you use private registries, you must override specific image values for the different subcharts and container images.

Our utility helps override image values for GitOps Runtimes by creating`values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these`values` files to override the images, as needed.

For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.

Repository certificates are required to authenticate users to on-premises Git servers.

If your Git servers are on-premises, add the repository certificates to your Codefresh`values` file, in`.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this[section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.

{% highlight yaml %}

global:

codefresh:

tls:

caCerts:

# optional - use an existing secret that contains the cert

# secretKeyRef:

# name: my-certificate-secret

# key: ca-bundle.crt

# or create "codefresh-tls-certs" secret

secret:

create: true

content: |

-----BEGIN CERTIFICATE-----

...

-----END CERTIFICATE-----

{% endhighlight yaml %}

{% endif %}

The Helm chart is published at oci://quay.io/codefresh/charts/csdp-add-cluster. You can see the source templates at[https://github.com/codefresh-io/csdp-official/tree/main/add-cluster/helm](https://github.com/codefresh-io/csdp-official/tree/main/add-cluster/helm){:target="\_blank"}.

To deploy the chart:

1. Copy[https://github.com/codefresh-io/csdp-official/blob/main/add-cluster/helm/values.yaml](https://github.com/codefresh-io/csdp-official/blob/main/add-cluster/helm/values.yaml){:target="\_blank"} locally.

1. Copythe[values.yaml](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/values.yaml){:target="\_blank"} file locally.

1. Fill in the required values.

1. Run:

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.

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

Review how Codefresh[validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).

After installation, you can:

* Continue with the Configuration & Management steps in the installation wizard. See[Configure GitOps Runtime]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/#configure-gitops-runtime).

OR

* View the installed Runtime in the Runtimes page, and complete the configuration at a later time.

* View the installed Runtime in the Runtimes page.

* Depending on your setup, complete the post-installation configuration:

* For private registries, you need to[override specific image values](#image-overrides-for-private-registries).

* If your Git servers are on-premises,[add custom repository certificates](#custom-repository-certificates).

After installation, go to**GitOps Runtimes > List View**:

%}

If you use private registries, you must override specific image values for the different subcharts and container images.

Our utility helps override image values for GitOps Runtimes by creating`values` files that match the structure of the subcharts, allowing you to easily replace image registries. During chart installation, you can provide these`values` files to override the images, as needed.

For more details, see[ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime#using-with-private-registries---helper-utility){:target="\_blank"}.

Repository certificates are required to authenticate users to on-premises Git servers.

If your Git servers are on-premises, add the repository certificates to your Codefresh`values` file, in`.values.argo-cd`. These values are used by the Argo CD that Codefresh deploys. For details on adding repository certificates, see this[section](https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.29.2-cap-CR-18430/charts/argo-cd/values.yaml#LL336C7-L336C7){:target="\_blank"}.

{% highlight yaml %}

global:

codefresh:

tls:

caCerts:

# optional - use an existing secret that contains the cert

# secretKeyRef:

# name: my-certificate-secret

# key: ca-bundle.crt

# or create "codefresh-tls-certs" secret

secret:

create: true

content: |

-----BEGIN CERTIFICATE-----

...

-----END CERTIFICATE-----

{% endhighlight yaml %}

You can also use Terraform to install additional GitOps Runtimes with the[Helm provider](https://registry.terraform.io/providers/hashicorp/helm/latest/docs){:target="\_blank"}.

You can get the values for both the Codefresh API token and account ID from the Codefresh UI as explained in the previous section.

The example is valid for the tunnel-based access mode. For ingress-based or service-mesh-based access modes, add the required arguments and values, as described in[GitOps Runtimes with ingress controllers/service meshes]({{site.baseurl}}/docs/installation/gitops/runtime-install-ingress-service-mesh-access-mode/).

Depending on your configuration, if you have private registries, you need to override specific image values, and if your Git servers are on-premises, you need to add custom repository certificates. See[Optional GitOps Runtime configuration](#optional-gitops-runtime-configuration) in this article.

By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add[Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use[Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and[create and deploy Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).

[Configuring GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/)

[Upgrading GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/manage-runtimes/#upgrade-gitops-runtimes/)

If auto-detection is not feasible, configure the names and ports for each of the Argo CD services in the Runtime's`values.yaml` file located[here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/installation/gitops/){:target="\_blank"}.

If auto-detection is not feasible, configure the names and ports for each of the Argo CD services in the Runtime's`values.yaml` file located[here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/values.yaml){:target="\_blank"}.

Here's an example of the service configuration in`values.yaml`.