codefresh-io · NimRegev · Jun 15, 2023 · Jun 15, 2023 · Jun 15, 2023 · Jun 15, 2023
@@ -281,8 +281,7 @@
       localurl: /docs/reference/git-tokens/ 
     - title: Secrets for GitOps
       localurl: /docs/reference/secrets   
-    - title: Shared configuration repo
-      localurl: /docs/reference/shared-configuration/
+
 
 
 - title: "Incubation"

@@ -516,6 +516,8 @@
           url: "/on-prem-gitops-runtime-install"  
         - title: Managing & monitoring GitOps Runtimes
           url: "/monitor-manage-runtimes"
+        - title: Shared Configuration Repository
+          url: "/shared-configuration"
         - title: Add external clusters to GitOps Runtimes
           url: "/managed-cluster" 
         - title: Add Git Sources to to GitOps Runtimes
@@ -596,8 +598,6 @@
       url: "/git-tokens"
     - title: Secrets
       url: "/secrets"   
-    - title: Shared configuration repo
-      url: "/shared-configuration"
 
 - title: What's new
   url: "/whats-new"

@@ -6,7 +6,7 @@ sub_group: gitops
 toc: true
 ---
 
-Images from connected registries are displayed in a 
+
 
 
 ## Access the Images dashboard 
@@ -40,7 +40,7 @@ Most image filters support multi-selection.  Unless otherwise indicated, the fil
 | **Git branch**       | Available in **More filters**. The Git branch to which the image is pushed.|
 | **Git repositories** | Available in **More filters**. The Git provider you use.|   
 
-Currently Deployed
+
 
 ## Image main view: deployment and repo information
 The main view of the Images dashboard displays high-level deployment, repository, and registry information. 

@@ -257,7 +257,7 @@ max-width="50%"
 %}
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -255,7 +255,7 @@ max-width="50%"
 
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  

@@ -248,7 +248,7 @@ max-width="50%"
 %}
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -85,7 +85,7 @@ use it.
 ## Related articles
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration//)  
 [Images]({{site.baseurl}}/docs/dashboards/images/)  
 [Monitoring applications]({{site.baseurl}}/docs/deployments/gitops/applications-dashboard/)    
 
@@ -95,7 +95,7 @@ For how-to instructions, see [Configure container registry integrations for GitO
 
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -42,7 +42,7 @@ The table describes the arguments required for Docker Hub GitOps integration in
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).  
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  

@@ -47,7 +47,7 @@ Before you configure settings in Codefresh to integrate GitHub container registr
 For how-to instructions, see [Configure container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#configure-container-registry-integrations-for-gitops-in-codefresh) and [Edit/delete container registry integrations for GitOps in Codefresh]({{site.baseurl}}/docs/gitops-integrations/container-registries/#editdelete-container-registry-integrations-for-gitops).  
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Issue-tracking GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -38,7 +38,7 @@ For how-to instructions, see [Configure container registry integrations for GitO
 
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [GitOps CI integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [GitOps issue-tracking integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -44,7 +44,7 @@ Make sure you have the:
 
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [GitOps CI integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [GitOps issue-tracking integrations]({{site.baseurl}}/docs/gitops-integrations/issue-tracking/)  
@@ -102,6 +102,6 @@ To enrich images with relevant information from Gerrit, incorporate Codefresh's
 Look for `CF_GERRIT_` in [CI integration argument reference]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/#ci-integration-argument-reference).  
 
 ## Related articles
-[Shared Configuration Repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repo]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/) 
@@ -69,7 +69,7 @@ use it.
    %}
 
 ### Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [CI GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Container registry GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)  
 
@@ -51,7 +51,7 @@ For pipelines based on GitHub Actions, configure the Jira integration in Codefre
 Codefresh uses the Secret Key stored in the runtime cluster to securely access Jira and retrieve the information. 
 
 ## Related articles
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration/)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)  
 [Image enrichment with GitOps integrations]({{site.baseurl}}/docs/gitops-integrations/image-enrichment-overview/)  
 [CI integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations/)  
 [Container registry integrations]({{site.baseurl}}/docs/gitops-integrations/container-registries/)  
@@ -96,6 +96,6 @@ Edit an existing Git Source by changing the source and destination definitions,
 
 ## Related articles
 [Monitoring & managing GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/monitor-manage-runtimes/)  
-[Shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration)  
 
 
@@ -156,7 +156,7 @@ max-width="80%"
 Once you authorize access, Codefresh creates two Git repositories, one to store the configuration settings for GitOps Runtimes, and the other to store the Runtime's application settings:
 * Shared Configuration Repository  
   The Shared Configuration Repository is a centralized Git repository that stores configuration settings for the Hosted GitOps Runtime. Additional Hybrid runtimes provisioned for the account can point to this repo to retrieve and reuse the configuration.  
-  Read about [Shared Configuration Repositories]({{site.baseurl}}/docs/reference/shared-configuration/).
+  Read about [Shared Configuration Repositories]({{site.baseurl}}/docs/installation/gitops/shared-configuration/).
 
 * Git Source application repo  
   Codefresh creates a Git Source application repo for every Hosted GitOps Runtime.  
@@ -215,8 +215,8 @@ image.html
 lightbox="true"
 file="/images/runtime/hosted-git-shared-repo.png"
 url="/images/runtime/hosted-git-shared-repo.png"
-alt="Shared configuration repo in Git"
-caption="Shared configuration repo in Git"
+alt="Shared Configuration Repository in Git"
+caption="Shared Configuration Repository in Git"
 max-width="70%"
 %}
 
@@ -227,8 +227,8 @@ image.html
 lightbox="true"
 file="/images/runtime/hosted-git-shared-repo.png"
 url="/images/runtime/hosted-git-shared-repo.png"
-alt="Shared configuration repo in Git"
-caption="Shared configuration repo in Git"
+alt="Shared Configuration Repository in Git"
+caption="Shared Configuration Repository in Git"
 max-width="70%"
 %}
 
@@ -323,7 +323,7 @@ See [Image enrichment with integrations]({{site.baseurl}}/docs/gitops-integratio
 ## Related articles
 [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)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration)  
 [Home Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard/)   
 [DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/)
 
@@ -1,5 +1,5 @@
 ---
-title: "Hybrid GitOps Helm Runtime installation"
+title: "Hybrid GitOps Runtime installation"
 description: "Provision Hybrid GitOps Runtimes through Helm"
 group: installation
 redirect_from:
@@ -177,7 +177,7 @@ The table below lists the settings validated in the `values` file.
 
 ### Step 3: Set up GitOps Git provider
 Select the Git provider, define the provider's API URL, and the Shared Configuration Repository for your account.
-The [Shared Configuration Repository]({{site.baseurl}}/docs/reference/shared-configuration/) is a Git repository with configuration manifests shared between all the Hybrid GitOps Runtimes within the same account.
+The [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/) is a Git repository with configuration manifests shared between all the Hybrid GitOps Runtimes within the same account.
 
 >**NOTE**:
  This is a one-time action, required once per account. 

@@ -47,7 +47,7 @@ There are two parts to installing a Hybrid GitOps Runtime:
   Every Hybrid GitOps Runtime installation makes commits to three Git repos:
   * Runtime install repo: The installation repo that manages the Hybrid Runtime itself with Argo CD. If the repo URL does not exist, it is automatically created during installation.
   * Git Source repo: Created automatically during Runtime installation. The repo where you store manifests for pipelines and applications. See [Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources).
-  * Shared configuration repo: Created for the first GitOps Runtime installed in your account. The repo stores configuration manifests for account-level resources and is shared with other GitOps Runtimes in the same account. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration).
+  * Shared configuration repo: Created for the first GitOps Runtime installed in your account. The repo stores configuration manifests for account-level resources and is shared with other GitOps Runtimes in the same account. See [Shared configuration repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration).
 
 
 
@@ -977,7 +977,7 @@ For both CLI wizard and Silent install:
 ### Git provider and repo flags
 The Git provider defined for the Runtime. 
 
->Because Codefresh creates a [shared configuration repo]({{site.baseurl}}/docs/reference/shared-configuration) for the Runtimes in your account, the Git provider defined for the first Runtime you install in your account is used for all the other Runtimes in the same account.  
+>Because Codefresh creates a [shared configuration repo]({{site.baseurl}}/docs/installation/gitops/shared-configuration) for the Runtimes in your account, the Git provider defined for the first Runtime you install in your account is used for all the other Runtimes in the same account.  
 
 You can define any of the following Git providers:
 * GitHub:
@@ -1215,7 +1215,7 @@ For _on-premises installations_, if the Ingress controller does not have a valid
 * Runtime install repository: The installation repo contains three folders: apps, bootstrap and projects, to manage the runtime itself with Argo CD.  
 * Git source repository: Created with the name `[repo_name]_git-source`. This repo stores manifests for pipelines with sources, events, workflow templates. See [Add Git Sources to runtimes]({{site.baseurl}}/docs/runtime/git-sources/).
 
-* Shared configuration repository: Stores configuration and resource manifests that can be shared across runtimes, such as integration resources. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration/)
+* Shared configuration repository: Stores configuration and resource manifests that can be shared across runtimes, such as integration resources. See [Shared configuration repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration/)
 
 **Argo CD components**  
 * Project, comprising an Argo CD AppProject and an ApplicationSet
@@ -1314,5 +1314,5 @@ data:
 [Add external clusters to Hybrid and Hosted Runtimes]({{site.baseurl}}/docs/installation/gitops/managed-cluster/)  
 [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)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration)  
 [Troubleshoot Hybrid Runtime installation]({{site.baseurl}}/docs/kb/articles/runtime-issues/)
@@ -366,7 +366,7 @@ Uninstalling a GitOps Runtime permanently removes:
 1. Click **Close** to exit the upgrade panel.
 
 ## Reset Shared Configuration Repository for GitOps Runtimes
-Codefresh creates and validates the [Shared Configuration Repository]({{site.baseurl}}/docs/reference/shared-configuration) when you install the first Hybrid or Hosted GitOps Runtime for your account, and uses it for all GitOps Runtimes you add to the same account.
+Codefresh creates and validates the [Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration) when you install the first Hybrid or Hosted GitOps Runtime for your account, and uses it for all GitOps Runtimes you add to the same account.
 
 Once created, you can reset the Shared Configuration Repo defined for your account under the following conditions:
 
@@ -738,6 +738,6 @@ The Activity Log is a quick way to monitor notifications for Runtime events such
 ## Related articles
 [Add Git Sources to GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/git-sources/)  
 [Add external clusters to GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/managed-cluster/)  
-[Shared configuration repo for GitOps Runtimes]({{site.baseurl}}/docs/reference/shared-configuration)  
+[Shared Configuration Repository]({{site.baseurl}}/docs/installation/gitops/shared-configuration)