From 319b1e619b91c429011782892b3b1332acc4a456 Mon Sep 17 00:00:00 2001
From: NimRegev <nima.regev@codefresh.io>
Date: Wed, 26 Oct 2022 16:36:56 +0300
Subject: [PATCH 1/4] Update requirements.md

---
 _docs/runtime/requirements.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_docs/runtime/requirements.md b/_docs/runtime/requirements.md
index ec2a3f68..e08b366c 100644
--- a/_docs/runtime/requirements.md
+++ b/_docs/runtime/requirements.md
@@ -21,7 +21,7 @@ The requirements listed are the **_minimum_** requirements to provision **_hybri
 {: .table .table-bordered .table-hover}
 | Item                     | Requirement            |  
 | --------------         | --------------           |  
-|Kubernetes cluster      | Server version 1.18 and higher, without Argo Project components. {::nomarkdown}<br><b>Tip</b>:  To check the server version, run:<br> <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">kubectl version --short</span>.{:/}|
+|Kubernetes cluster      | Server version 1.21.0 and higher, without Argo Project components. {::nomarkdown}<br><b>Tip</b>:  To check the server version, run:<br> <span style="font-family: var(--font-family-monospace); font-size: 87.5%; color: #ad6800; background-color: #fffbe6">kubectl version --short</span>.{:/}|
 | Ingress controller| Configured on Kubernetes cluster and exposed from the cluster. {::nomarkdown} <br>Supported and tested ingress controllers include: <ul><li>Ambassador</li>{:/}(see [Ambassador ingress configuration](#ambassador-ingress-configuration)){::nomarkdown}<li>AWS ALB (Application Load Balancer)</li>{:/} (see [AWS ALB ingress configuration](#aws-alb-ingress-configuration)){::nomarkdown}<li>Istio</li>{:/} (see [Istio ingress configuration](#istio-ingress-configuration)){::nomarkdown}<li>NGINX Enterprise (nginx.org/ingress-controller)</li>{:/} (see [NGINX Enterprise ingress configuration](#nginx-enterprise-ingress-configuration)){::nomarkdown}<li>NGINX Community (k8s.io/ingress-nginx)</li> {:/} (see [NGINX Community ingress configuration](#nginx-community-version-ingress-configuration)){::nomarkdown}<li>Trafik</li>{:/}(see [Traefik ingress configuration](#traefik-ingress-configuration))|
 |Node requirements| {::nomarkdown}<ul><li>Memory: 5000 MB</li><li>CPU: 2</li></ul>{:/}|
 |Cluster permissions | Cluster admin permissions |

From 32e5fac83b1a9ac73e1c9cd7fd9fda15692d231e Mon Sep 17 00:00:00 2001
From: NimRegev <nima.regev@codefresh.io>
Date: Sun, 30 Oct 2022 13:12:54 +0200
Subject: [PATCH 2/4] Update installation

Added shared repo to runtime repo list
---
 _docs/runtime/installation-options.md | 2 +-
 _docs/runtime/installation.md         | 7 ++++---
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/_docs/runtime/installation-options.md b/_docs/runtime/installation-options.md
index 0d2a6281..534ae234 100644
--- a/_docs/runtime/installation-options.md
+++ b/_docs/runtime/installation-options.md
@@ -50,7 +50,7 @@ Codefresh Runtime creates three repositories in your organization's Git provider
 
 * Codefresh runtime installation repository
 * Codefresh Git Sources
-* Codefresh shared configuration repository. 
+* Codefresh shared configuration repository
 
 <!---**Codefresh Runtime functionality**  
 
diff --git a/_docs/runtime/installation.md b/_docs/runtime/installation.md
index c25b7d84..b9043913 100644
--- a/_docs/runtime/installation.md
+++ b/_docs/runtime/installation.md
@@ -14,10 +14,11 @@ There are two parts to installing a hybrid runtime:
 1. Installing the Codefresh CLI
 2. Installing the hybrid runtime from the CLI, either through the CLI wizard or via silent installation through the installation flags.  
   The hybrid runtime is installed in a specific namespace on your cluster. You can install more runtimes on different clusters in your deployment.  
-  Every hybrid runtime installation makes commits to two Git repos:
+  Every hybrid 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, runtime creates it automatically.
-  * Git Source repo: Created automatically during runtime installation. The repo where you store manifests to run CodefreshCodefresh pipelines.
+  * 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 runtime installation.
+  * Git Source repo: Created automatically during runtime installation. The repo where you store manifests for pipelines and applications.
+  * Shared configuration repo: Created for the first runtime in a user account. The repo stores configuration manifests for account-level resources and is shared with other runtimes in the same account.
 
 See also [Codefresh architecture]({{site.baseurl}}/docs/getting-started/architecture).
 

From e57848afda23953b02ad57a674543ce99bad8c01 Mon Sep 17 00:00:00 2001
From: NimRegev <nima.regev@codefresh.io>
Date: Mon, 31 Oct 2022 09:48:03 +0200
Subject: [PATCH 3/4] Update installation.md

Added xrefs to Git sources and shared repo
---
 _docs/runtime/installation.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/_docs/runtime/installation.md b/_docs/runtime/installation.md
index b9043913..0b86355e 100644
--- a/_docs/runtime/installation.md
+++ b/_docs/runtime/installation.md
@@ -17,8 +17,8 @@ There are two parts to installing a hybrid runtime:
   Every hybrid 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 runtime installation.
-  * Git Source repo: Created automatically during runtime installation. The repo where you store manifests for pipelines and applications.
-  * Shared configuration repo: Created for the first runtime in a user account. The repo stores configuration manifests for account-level resources and is shared with other runtimes in the same account.
+  * Git Source repo: Created automatically during runtime installation. The repo where you store manifests for pipelines and applications. See [Git Sources]({{site.baseurl}}/docs/runtime/git-sources).
+  * Shared configuration repo: Created for the first runtime in a user account. The repo stores configuration manifests for account-level resources and is shared with other runtimes in the same account. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration).
 
 See also [Codefresh architecture]({{site.baseurl}}/docs/getting-started/architecture).
 

From 4008d4db3317d457cacb46d6a83e6d8ef489c7ad Mon Sep 17 00:00:00 2001
From: NimRegev <nima.regev@codefresh.io>
Date: Mon, 31 Oct 2022 09:51:14 +0200
Subject: [PATCH 4/4] Update installation.md

---
 _docs/runtime/installation.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/_docs/runtime/installation.md b/_docs/runtime/installation.md
index 0b86355e..9ad941d4 100644
--- a/_docs/runtime/installation.md
+++ b/_docs/runtime/installation.md
@@ -15,7 +15,6 @@ There are two parts to installing a hybrid runtime:
 2. Installing the hybrid runtime from the CLI, either through the CLI wizard or via silent installation through the installation flags.  
   The hybrid runtime is installed in a specific namespace on your cluster. You can install more runtimes on different clusters in your deployment.  
   Every hybrid 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 runtime 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/runtime/git-sources).
   * Shared configuration repo: Created for the first runtime in a user account. The repo stores configuration manifests for account-level resources and is shared with other runtimes in the same account. See [Shared configuration repository]({{site.baseurl}}/docs/reference/shared-configuration).