Jun 8, 2023 · Feb 28, 2023 · Feb 28, 2023 · Feb 28, 2023 · Feb 28, 2023 · Feb 28, 2023
diff --git a/_data/home-content.yml b/_data/home-content.yml
    - title: On-Premises upgrade
      localurl: /docs/installation/codefresh-on-prem-upgrade/
    - title: Hosted GitOps installation
      localurl: /docs/installation/gitops/hosted-runtime/
    - title: Hybrid GitOps installation
      localurl: /docs/installation/gitops/hybrid-gitops/
      localurl: /docs/installation/gitops/hosted-runtime/
    - title: Hybrid GitOpsHelminstallation
      localurl: /docs/installation/gitops/hybrid-gitops-helm-installation/



diff --git a/_data/nav.yml b/_data/nav.yml
      url:
      sub-pages:
        - title: Hosted GitOps Runtime
          url: "/hosted-runtime"
        - title: Hybrid GitOps Runtime
          url: "/hybrid-gitops"
          url: "/hosted-runtime"
        - title: Hybrid GitOpsHelmRuntime
          url: "/hybrid-gitops-helm-installation"
        - title: Managing & monitoring GitOps Runtimes
          url: "/monitor-manage-runtimes"
        - title: Add external clusters to GitOps Runtimes
diff --git a/_docs/installation/gitops/hybrid-gitops-helm-installation.md b/_docs/installation/gitops/hybrid-gitops-helm-installation.md
diff --git a/_docs/installation/gitops/hybrid-gitops.md b/_docs/installation/gitops/hybrid-gitops.md
 description: "Provision Hybrid GitOps Runtimes"
 group: installation
 sub_group: gitops
 redirect_from:
  - /csdp-docs/docs/runtime/installation/
  - /csdp-docs/docs/runtime/requirements/
 toc: true
 ---

 >ATTENTION:
  >We have transitioned to a Helm-based installation for Hybrid GitOps Runtimes, for improved experience and performance.

  >The CLI-based installation for Hybrid GitOps is now considered legacy. We will deprecate this installation mode permanently on 18 June 2023.
  >To migrate your Hybrid GitOps Runtimes from CLI to Helm, please contact us, and we'll migrate them for you.


 Provision one or more Hybrid GitOps Runtimes in your Codefresh account.
 Start by reviewing [system requirements](#minimum-system-requirements) for Hybrid GitOps.
 If you are installing with ingress-controllers, you must configure them as required _before_ starting the installation.
 [Monitoring & managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/)
 [Add Git Sources to runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/)
 [Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration)
 [Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/troubleshooting/runtime-issues/)
 [Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/kb/articles/runtime-issues/)
diff --git a/_docs/installation/gitops/monitor-manage-runtimes.md b/_docs/installation/gitops/monitor-manage-runtimes.md
diff --git a/_docs/reference/shared-configuration.md b/_docs/reference/shared-configuration.md
 ---
 title: "Sharedconfiguration repo"
 description: ""
 title: "SharedConfiguration Repository"
 description: "Share configuration settings across GitOps Runtimes"
 group: reference
 toc: true
 ---


 A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyruntime.
 A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyGitOps Runtime.

 * Hosted GitOpsruntimes
  As part of the setup for a Hosted GitOps runtime, Codefresh creates theshared configuration repository in the selected organization, together with the default Git Source repo. See [Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.
 * Hosted GitOpsRuntimes
  As part of the setup for a Hosted GitOps runtime, Codefresh creates theShared Configuration Repository in the selected organization, together with the default Git Source repo. See [Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.

 * Hybridruntimes
  When you install the firsthybridruntime for an account, youcan manually define the shared configuration repo through the `--shared-config-repo` flag. Or, you can allow Codefreshtoautomatically createtheshared configuration repo in the runtime installation repo, in `shared-config` root.See [Installinghybrid runtimes]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#install-hybrid-gitops-runtime).
 * HybridGitOps Runtimes
  When you install the firstHybrid GitOpsruntime for an account, youare requiredtodefinetheShared Configuration Repo as part of setting up your Git account.See [InstallingHybrid GitOps Helm Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#step-3-set-up-gitops-git-account).

  For older versions of hybrid runtimes, upgrade the runtime to create the shared configuration repo, as described in [Upgrading hybrid runtimes](#upgrading-hybrid-runtimes) later in this article.

 > Currently, Codefresh supports a singleshared configuration repo per account.
  Youcan alsoreset theshared configuration repo if needed. See [Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).
 > Currently, Codefresh supports a singleShared Configuration Repo per account.
  Youmay need toreset theShared Configuration Repo after creating it. See [Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).


 ## Sharedconfiguration repo structure
 ## SharedConfiguration Repo structure
 Below is a representation of the structure of the repository with the shared configuration.
 See a [sample repo](https://github.dev/noam-codefresh/shared-gs){:target="\_blank"}.



 ## Git Source application per runtime
 In addition to the application manifests forthe runtimes in the shared configuration repository, everyruntime has a Git Source application that references `runtimes/<runtime-name>`.
 In addition to the application manifests forGitOps Runtimes in the shared configuration repository, everyGitOps Runtime has a Git Source application that references `runtimes/<runtime-name>`.

 This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theruntime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.
 This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theGitOps Runtime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.


 ## Adding resources
 When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theruntimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.
 When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theGitOps Runtimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.

 <!--
 ## Upgrading hybrid runtimes
 Older hybrid runtimes that do not have the shared configuration repository must be upgraded to the latest version.
 You have two options to define the shared configuration repository during upgrade:

 If the hybrid runtime being upgraded has managed clusters, once the shared configuration repo is created for the account either automatically or manually on upgrade, all clusters are migrated to the same repo when app-proxy is initialized. An Argoproj application manifest is committed to the repo for each cluster managed by the runtime.

 See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes).
 See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes).  -->



diff --git a/images/icons/current-state-degraded-old.png b/images/icons/current-state-degraded-old.png
diff --git a/images/icons/current-state-healthy-old.png b/images/icons/current-state-healthy-old.png
diff --git a/images/icons/current-state-missing-old.png b/images/icons/current-state-missing-old.png
diff --git a/images/icons/current-state-out-of-sync-old.png b/images/icons/current-state-out-of-sync-old.png
diff --git a/images/icons/current-state-progressing-old.png b/images/icons/current-state-progressing-old.png
diff --git a/images/icons/current-state-suspended-old.png b/images/icons/current-state-suspended-old.png
diff --git a/images/icons/current-state-sync-unknown.png b/images/icons/current-state-sync-unknown.png
diff --git a/images/icons/current-state-synced-old.png b/images/icons/current-state-synced-old.png
diff --git a/images/icons/current-state-synced1.png b/images/icons/current-state-synced1.png
diff --git a/images/icons/current-state-syncing-old.png b/images/icons/current-state-syncing-old.png
diff --git a/images/icons/current-state-unknown-old.png b/images/icons/current-state-unknown-old.png
diff --git a/images/icons/local-cluster.png b/images/icons/local-cluster.png
diff --git a/images/icons/managed-cluster.png b/images/icons/managed-cluster.png
diff --git a/images/icons/runtime-hover.png b/images/icons/runtime-hover.png
diff --git a/images/icons/runtime-out-of-sync.png b/images/icons/runtime-out-of-sync.png
diff --git a/images/icons/runtime-synced.png b/images/icons/runtime-synced.png
diff --git a/images/icons/runtime-syncing.png b/images/icons/runtime-syncing.png
diff --git a/images/icons/runtime-topology-add-cluster.png b/images/icons/runtime-topology-add-cluster.png
diff --git a/images/icons/runtime-topology-in-cluster.png b/images/icons/runtime-topology-in-cluster.png
diff --git a/images/icons/runtime-topology-managed-cluster.png b/images/icons/runtime-topology-managed-cluster.png
diff --git a/images/icons/runtime-topology-name.png b/images/icons/runtime-topology-name.png
diff --git a/images/runtime/runtime-list-view.png b/images/runtime/runtime-list-view.png
diff --git a/images/runtime/shared-config-repo-missing.png b/images/runtime/shared-config-repo-missing.png
Original file line number	Diff line number	Diff line change
Expand Up		@@ -231,9 +231,9 @@
		- title: On-Premises upgrade
		localurl: /docs/installation/codefresh-on-prem-upgrade/
		- title: Hosted GitOps installation
		localurl: /docs/installation/gitops/hosted-runtime/
		- title: Hybrid GitOps installation
		localurl: /docs/installation/gitops/hybrid-gitops/
		localurl: /docs/installation/gitops/hosted-runtime/
		- title: Hybrid GitOpsHelminstallation
		localurl: /docs/installation/gitops/hybrid-gitops-helm-installation/



Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -502,9 +502,9 @@
		url:
		sub-pages:
		- title: Hosted GitOps Runtime
		url: "/hosted-runtime"
		- title: Hybrid GitOps Runtime
		url: "/hybrid-gitops"
		url: "/hosted-runtime"
		- title: Hybrid GitOpsHelmRuntime
		url: "/hybrid-gitops-helm-installation"
		- title: Managing & monitoring GitOps Runtimes
		url: "/monitor-manage-runtimes"
		- title: Add external clusters to GitOps Runtimes
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -3,9 +3,19 @@ title: "Hybrid GitOps Runtime installation"
		description: "Provision Hybrid GitOps Runtimes"
		group: installation
		sub_group: gitops
		redirect_from:
		- /csdp-docs/docs/runtime/installation/
		- /csdp-docs/docs/runtime/requirements/
		toc: true
		---

		>ATTENTION:
		>We have transitioned to a Helm-based installation for Hybrid GitOps Runtimes, for improved experience and performance.

		>The CLI-based installation for Hybrid GitOps is now considered legacy. We will deprecate this installation mode permanently on 18 June 2023.
		>To migrate your Hybrid GitOps Runtimes from CLI to Helm, please contact us, and we'll migrate them for you.


		Provision one or more Hybrid GitOps Runtimes in your Codefresh account.
		Start by reviewing [system requirements](#minimum-system-requirements) for Hybrid GitOps.
		If you are installing with ingress-controllers, you must configure them as required _before_ starting the installation.
Expand DownExpand Up		@@ -1305,4 +1315,4 @@ data:
		[Monitoring & managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/)
		[Add Git Sources to runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/)
		[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration)
		[Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/troubleshooting/runtime-issues/)
		[Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/kb/articles/runtime-issues/)
Original file line number	Diff line number	Diff line change
		@@ -1,26 +1,25 @@
		---
		title: "Sharedconfiguration repo"
		description: ""
		title: "SharedConfiguration Repository"
		description: "Share configuration settings across GitOps Runtimes"
		group: reference
		toc: true
		---


		A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyruntime.
		A Codefresh account with a Hosted or a Hybrid GitOps runtime can store configuration manifests for account-level resources in a Git repository. This repository can be shared with other runtimes in the same account, avoiding the need to create and maintain different configuration manifests for everyGitOps Runtime.

		* Hosted GitOpsruntimes
		As part of the setup for a Hosted GitOps runtime, Codefresh creates theshared configuration repository in the selected organization, together with the default Git Source repo. See [Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.
		* Hosted GitOpsRuntimes
		As part of the setup for a Hosted GitOps runtime, Codefresh creates theShared Configuration Repository in the selected organization, together with the default Git Source repo. See [Connect Git provider]({{site.baseurl}}/docs/installation/gitops/hosted-runtime/#2-connect-git-provider) in Hosted GitOps setup.

		* Hybridruntimes
		When you install the firsthybridruntime for an account, youcan manually define the shared configuration repo through the `--shared-config-repo` flag. Or, you can allow Codefreshtoautomatically createtheshared configuration repo in the runtime installation repo, in `shared-config` root.See [Installinghybrid runtimes]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops/#install-hybrid-gitops-runtime).
		* HybridGitOps Runtimes
		When you install the firstHybrid GitOpsruntime for an account, youare requiredtodefinetheShared Configuration Repo as part of setting up your Git account.See [InstallingHybrid GitOps Helm Runtime installation]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#step-3-set-up-gitops-git-account).

		For older versions of hybrid runtimes, upgrade the runtime to create the shared configuration repo, as described in [Upgrading hybrid runtimes](#upgrading-hybrid-runtimes) later in this article.

		> Currently, Codefresh supports a singleshared configuration repo per account.
		Youcan alsoreset theshared configuration repo if needed. See [Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).
		> Currently, Codefresh supports a singleShared Configuration Repo per account.
		Youmay need toreset theShared Configuration Repo after creating it. See [Reset shared configuration repository for GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#reset-shared-configuration-repository-for-gitops-runtimes).


		## Sharedconfiguration repo structure
		## SharedConfiguration Repo structure
		Below is a representation of the structure of the repository with the shared configuration.
		See a [sample repo](https://github.dev/noam-codefresh/shared-gs){:target="\_blank"}.

Expand DownExpand Up		@@ -97,14 +96,15 @@ spec:


		## Git Source application per runtime
		In addition to the application manifests forthe runtimes in the shared configuration repository, everyruntime has a Git Source application that references `runtimes/<runtime-name>`.
		In addition to the application manifests forGitOps Runtimes in the shared configuration repository, everyGitOps Runtime has a Git Source application that references `runtimes/<runtime-name>`.

		This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theruntime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.
		This Git Source application creates an application manifest with the `<cluster-name>` for every cluster managed by theGitOps Runtime. The `include` field in the `<cluster-name>` application manifest determines which subdirectories in the `resources` directory are synced to the target cluster.


		## Adding resources
		When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theruntimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.
		When creating a new resource, such as a new integration for example in the Codefresh UI, you can define theGitOps Runtimes and clusters to which to apply that resource. The app-proxy saves the resource in the correct location and updates the relevant Argo CD Applications to include it.

		<!--
		## Upgrading hybrid runtimes
		Older hybrid runtimes that do not have the shared configuration repository must be upgraded to the latest version.
		You have two options to define the shared configuration repository during upgrade:
Expand All		@@ -115,7 +115,7 @@ You have two options to define the shared configuration repository during upgrad

		If the hybrid runtime being upgraded has managed clusters, once the shared configuration repo is created for the account either automatically or manually on upgrade, all clusters are migrated to the same repo when app-proxy is initialized. An Argoproj application manifest is committed to the repo for each cluster managed by the runtime.

		See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes).
		See [(Hybrid) Upgrade provisioned runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/#hybrid-gitops-upgrade-provisioned-runtimes). -->



Expand Down