You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/runtime/installation-options.md
+7-6Lines changed: 7 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ toc: true
8
8
Codefresh supports two installation environments:
9
9
10
10
11
-
***Hosted** environments (Beta), with Argo CD installed in the Codefresh cluster.
11
+
***Hosted** environments, with Argo CD installed in the Codefresh cluster.
12
12
The runtime is installed and provisioned in a Codefresh cluster, and managed by Codefresh.
13
13
Hosted enviroments are full-cloud environments, where all updates and improvements are managed by Codefresh, with zero-maintenance overhead for you as the customer. Currently, you can add one hosted runtime per account.
14
14
For the architecture illustration, see[Hosted runtime architecture]({{site.baseurl}}/docs/getting-started/architecture/#hosted-runtime-architecture).
@@ -17,8 +17,8 @@ Codefresh supports two installation environments:
@@ -50,13 +50,14 @@ Codefresh Runtime creates three repositories in your organization's Git provider
50
50
51
51
* Codefresh runtime installation repository
52
52
* Codefresh Git Sources
53
-
* Codefresh shared configuration repository. It does so for two types of entities:
53
+
* Codefresh shared configuration repository.
54
+
55
+
<!---**Codefresh Runtime functionality**
54
56
55
-
**Codefresh Runtime finctionality**
56
57
The runtime:
57
58
* Ensures that the installation repository and the Git Sources are always in sync, and applies Git changes back to the cluster
58
59
* Receives events and information from the user's organization systems to execute workflows
59
-
By default, the ingress controller directs all requests and events to the Codefresh Application Proxy. When internal andanexternal ingress hosts are configured, the ingress comtroller directs webhook events to the relevant Event Source and then to Argo Events (not via the Codefresh Application Proxy).
60
+
By default, the ingress controller directs all requests and events to the Codefresh Application Proxy. When internal and external ingress hosts are configured, the ingress comtroller directs webhook events to the relevant Event Source and then to Argo Events (not via the Codefresh Application Proxy).-->