localurl:/docs/installation/gitops/hybrid-gitops-helm-installation/

-title:On-premises GitOps Runtime installation

localurl:/docs/installation/gitops/on-prem-gitops-runtime-install/

-title:Migrate Hybrid GitOps Runtimes from CLI to Helm

localurl:/docs/installation/gitops/migrate-cli-runtimes-helm/

-title:Administration

icon:images/home-icons/administration.svg

-title:Hybrid GitOps Runtime

url:"/hybrid-gitops-helm-installation"

-title:Hybrid GitOps Runtime alongside Community Argo CD

url:"/argo-with-gitops-side-by-side"

url:"/argo-with-gitops-side-by-side"

-title:On-premises GitOps Runtime

url:"/on-prem-gitops-runtime-install"

-title:Managing & monitoring GitOps Runtimes

-title:Migrating Hybrid GitOps Runtimes from CLI to Helm

url:"/migrate-cli-runtimes-helm"

-title:Monitoring & managing GitOps Runtimes

url:"/monitor-manage-runtimes"

-title:Shared Configuration Repository

url:"/shared-configuration"

-title:Add external clusters to GitOps Runtimes

-title:Adding external clusters to GitOps Runtimes

url:"/managed-cluster"

-title:Add Git Sources to GitOps Runtimes

-title:Adding Git Sources to GitOps Runtimes

url:"/git-sources"

-title:Download/upgrade GitOps CLI

url:"/upgrade-gitops-cli"

title:"Add Git Sources to GitOps Runtimes"

title:"Adding Git Sources to GitOps Runtimes"

description:"Manage Git Sources storing resources"

group:installation

toc:true

toc:true

We have transitioned to a Helm-based installation for Hybrid GitOps Runtimes for improved experience and performance, which is now the default Runtime for GitOps.

The[CLI-based installation for Hybrid GitOps]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/) is considered legacy.

We will deprecate this installation mode permanently in the coming months. Please stay tuned for further updates and instructions, including guidelines on the migration process.

We have transitioned to a Helm-based installation for Hybrid GitOps Runtimes for improved experience and performance, which is now the default Runtime for GitOps. <br><br>

The CLI-based installation for Hybrid GitOps is considered legacy. We will deprecate this installation mode permanently in the coming months.<br>

You can migrate existing CLI-based GitOps Runtimes to Helm-based ones, as described in[Migrating GitOps Runtimes from CLI to Helm]({{site.baseurl}}/docs/installation/gitops/migrate-cli-runtimes-helm/).

This article walks you through the process of installing Hybrid GitOps Runtimes in your Codefresh accounts using Helm charts. You can install a single GitOps Runtime on a cluster. To install additional Runtimes in the same account, each account must be on a different cluster. Every Runtime within your account must have a unique name.

--set global.runtime.ingress.enabled=true\

--set "global.runtime.ingress.hosts[0]"=<ingress-host>\

--set global.runtime.ingress.className=<ingress-class>\

<helm-repo-name>/gitops-runtime\

--set argo-cd.fullnameOverride=codefresh-argo-cd\

--set argo-rollouts.fullnameOverride=codefresh-argo-cd\

--set argo-cd.configs.cm.application.resourceTrackingMethod=annotation\

oci://quay.io/codefresh/gitops-runtime\

--wait

{% endhighlight %}

<br>

--set global.runtime.ingressUrl=<ingress-url>\

--set global.runtime.ingress.enabled=false\

--set tunnel-client.enabled=false\

<helm-repo-name>/gitops-runtime\

--set argo-cd.fullnameOverride=codefresh-argo-cd\

--set argo-rollouts.fullnameOverride=codefresh-argo-cd\

--set argo-cd.configs.cm.application.resourceTrackingMethod=annotation\

oci://quay.io/codefresh/gitops-runtime\

--wait

{% endhighlight %}

*`<codefresh-account-id>` is mandatory only for_tunnel-based Hybrid GitOps Runtimes_ , which is also the default access mode. Automatically populated by Codefresh in the installation command.

*`<codefresh-api-key>` is the API key, either an existing one or a new API key you generated. When generated, it is automatically populated in the command.

*`<runtime-name>` is the name of the GitOps Runtime, and is either`codefresh` which is the default, or the custom name you define.

*`<helm-repo-name>` is the name of the repo in which to store the Helm chart, and must be identical to the`<hem-repo-name>` you defined in_step 3_, either`cf-gitops-runtime` which is the default, or any custom name you define.

*`gitops-runtime` is the chart name defined by Codefresh, and cannot be changed.

* GitOps with Argo CD installation:

*`argo-cd.fullnameOverride=codefresh-argo-cd` is mandatory when_installing GitOps with Argo CD_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.

{:start="5"}

1. Wait for a few minutes, and then click**Close**.

You are taken to the List View for GitOps Runtimes where:

* The Hybrid GitOps Runtime you added is prefixed with a green dot indicating that it is online

* The Type column for the Runtime displays**Helm**

* The Hybrid GitOps Runtime you added is prefixed with a green dot indicating that it is online.

* The Type column for the Runtime displays**Helm**.

* The Sync Status column displays**Complete Installation**, indicating that there are pending steps to complete the installation.

* Drilling down into the Runtime shows empty tabs for Runtime Components, Git Sources, and Managed Clusters.

The Runtime Components are populated only when the GitOps Runtime is configured as an Argo Application, described later on in the installation process.

Git credentials include authorizing access to Git through OAuth2 or a Git Runtime token, and optionally configuring SSH access to the Git installation repo for the Runtime.

**Git authorization**

* OAuth2 authorization is possible if your admin has registered an OAuth Application for Codefresh. See[OAuth2 setup forCodefresh]({{site.baseurl}}/docs/administration/account-user-management/oauth-setup/).

* OAuth2 authorization is possible if your admin has registered an OAuth Application for Codefresh. See[OAuth2 setup forGitOps]({{site.baseurl}}/docs/administration/account-user-management/oauth-setup/).

* Git access token authentication requires you to generate an access token in your Git provider account for the GitOps Runtime, with the correct scopes. See[GitOps Runtime token scopes]({{site.baseurl}}/docs/reference/git-tokens/#git-runtime-token-scopes).

**SSH access to Git**

**Shared Configuration Repository and Git provider**

The Shared Configuration Repository and Git provider are configured once per account, and not required for additional installations.

**Helm chart repository**

The repository for the Helm chart is also configured per account, and is not required for additional installations in the same account.

**Access mode**

You can define the tunnel/ingress/service-mesh-based access mode for the additional GitOps Runtimes you install. The command in the How To below 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 the step-by-step section,[Step 3: Install Hybrid GitOps Runtime](#step-3-install-hybrid-gitops-runtime).

title:"Add external clusters to GitOps Runtimes"

title:"Adding external clusters to GitOps Runtimes"

description:"Manage multiple remote clusters with a GitOps Runtime"

group:installation

sub_group:gitops