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
* Remove community argo contentRemoved community argo content from relevant topics* Fix errors* Update runtime-install-ingress-service-mesh-access-mode.md
Copy file name to clipboardExpand all lines: _docs/installation/gitops.md
+2-9Lines changed: 2 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,8 +11,8 @@ Managing applications at scale requires efficient tools and practices. Codefresh
11
11
#####What is a GitOps Runtime?
12
12
The GitOps Runtime is a specialized component installed within your cluster, acting as a bridge between your infrastructure and the Codefresh platform. It integrates seamlessly with Argo CD, a leading tool for continuous delivery, and Argo Rollouts for advanced deployment strategies.
13
13
14
-
This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances.
15
-
By leveraging the Runtime, teams can efficiently orchestrate deployments, monitor environments, and ensure consistency across applications. To better understand how the Runtime manages key aspects like Git token usage and sharedconfig repos, see[GitOps Runtime concepts]({{site.baseurl}}/docs/installation/gitops/runtime-concepts/).
14
+
This Runtime forms the foundation of your GitOps operations, enabling centralized control and visibility across multiple Argo CD instances from a single control plane.
15
+
By leveraging the Runtime, teams can efficiently orchestrate deployments, monitor environments, and ensure consistency across applications. To better understand how the Runtime manages key aspects like Git token usage and sharedconfiguration, see[GitOps Runtime concepts]({{site.baseurl}}/docs/installation/gitops/runtime-concepts/).
16
16
17
17
{% include
18
18
image.html
@@ -50,13 +50,6 @@ No Argo CD yet? Deploy a new, fully managed instance of Argo CD with the GitOps
50
50
51
51
See[Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).
52
52
53
-
{% if page.collection != site.gitops_collection %}
54
-
#####Installation alongside Community Argo CD
55
-
Using Community Argo CD? Add Codefresh GitOps without disrupting your existing setup.
56
-
Requires additional configuration to manage resources separately and avoid interference with the existing Community Argo CD setup.
57
-
58
-
See[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
59
-
{% endif %}
60
53
61
54
You can install one GitOps Runtime per cluster. To add more, each Runtime must be on a separate cluster and have a unique name.
Copy file name to clipboardExpand all lines: _docs/installation/gitops/hybrid-gitops-helm-installation.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,8 @@ This article describes how to install the GitOps Runtime in a Codefresh accounts
14
14
The Codefresh`values.yaml` located[here](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/){:target="\_blank"}, contains all the arguments you can configure, including optional ones.
15
15
Review how Codefresh[validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).
16
16
17
-
{% if page.collection != site.gitops_collection %}
18
-
To install the GitOps Runtime:
19
-
* With an existing Argo CD instance, see[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/)
20
-
* Alongside your community Argo CD installation, see[Install GitOps Runtime alongside Community Argo CD]({{site.baseurl}}/docs/installation/gitops/argo-with-gitops-side-by-side/).
21
-
{% endif %}
17
+
To install the GitOps Runtime with an existing Argo CD instance, see[Install GitOps Runtime with existing Argo CD]({{site.baseurl}}/docs/installation/gitops/runtime-install-with-existing-argo-cd/).
Copy file name to clipboardExpand all lines: _docs/installation/gitops/runtime-install-ingress-service-mesh-access-mode.md
+7-28Lines changed: 7 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,18 +12,17 @@ In addition to the tunnel-based access mode which is is the default, the GitOps
12
12
The ingress controller configured on the same Kubernetes cluster as the GitOps Runtime, implements the ingress traffic rules for the GitOps Runtime.
13
13
***Service-mesh based access mode**
14
14
The runtime integrates with a service mesh for communication.
15
-
For details, see[GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).
15
+
For details, see[GitOps Runtime architecture]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/).
16
16
17
17
#####Pre-installation configuration
18
-
Configure ingress controllers and service meshes before installing the GitOps Runtime.
18
+
Configure ingress controllers and service meshes before installing the GitOps Runtime. See[Pre-installation: Configure ingress controllers/service meshes](#pre-installation-configure-ingress-controllersservice-meshes).
19
19
20
20
#####Installation command flags
21
-
The Runtime Install command requires additional flags to specify ingress or service-mesh compatibility.
22
-
If you are installing alongside Community Argo CD, the Runtime Install command requires additional flags.
21
+
The Runtime Install command requires additional flags to specify ingress or service-mesh compatibility. See[Install Runtime command for ingress-based/service-mesh based access modes](#installation-install-runtime-command-for-ingress-basedservice-mesh-based-access-modes).
23
22
24
23
25
24
#####Post-installation configuration
26
-
After installing the GitOps Runtime, specific ingress controllers and service meshes need additional configuration.
25
+
After installing the GitOps Runtime, specific ingress controllers and service meshes need additional configuration. See[Post-installation: Configure ingress controllers/service meshes](#post-installation-configure-ingress-controllersservice-meshes).
*`global.runtime.ingress.enabled=true`is mandatory for ingress-based Runtimes. Indicates the runtime is ingress-based.
59
53
*`<ingress-host>` is the IP address or hostname of the ingress controller. Mandatory for ingress-based Runtimes.
60
54
*`<ingress-class>` is the ingress class of the ingress controller (e.g.,`nginx` for the NGINX ingress controller). Mandatory for ingress-based Runtimes.
61
-
{% if page.collection != site.gitops_collection %}
62
-
**Community Argo CD only**
63
-
*`argo-cd.fullnameOverride=codefresh-argo-cd` is_mandatory_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.
64
-
*`argo-rollouts.fullnameOverride=codefresh-argo-rollouts` is_mandatory_ when you have Argo Rollouts in your cluster to avoid conflicts.
65
-
*`argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label` is_mandatory_ to avoid conflicts when tracking resources with the same application names or when tracking the same resource in both the Community Argo CD and GitOps Runtime's Argo CD.
66
-
{% endif %}
55
+
67
56
68
57
###Service-mesh-based install command (without ingress and tunnel)
69
58
Following are the additional flags you need to add to the install command for service-mesh based access modes.
@@ -72,24 +61,13 @@ Following are the additional flags you need to add to the install command for se
72
61
--set global.runtime.ingressUrl=<ingress-url>\
73
62
--set global.runtime.ingress.enabled=false\
74
63
--set tunnel-client.enabled=false\
75
-
{% if page.collection != site.gitops_collection %}
{% if page.collection != site.gitops_collection %}
88
-
**Community Argo CD only**
89
-
*`argo-cd.fullnameOverride=codefresh-argo-cd` is_mandatory_ to avoid conflicts at the cluster-level for resources in both the Community Argo CD and GitOps Runtime's Argo CD.
90
-
*`argo-rollouts.fullnameOverride=codefresh-argo-rollouts` is_mandatory_ when you have Argo Rollouts in your cluster to avoid conflicts.
91
-
*`argo-cd.configs.cm.application.resourceTrackingMethod=annotation+label` is_mandatory_ to avoid conflicts when tracking resources with the same application names or when tracking the same resource in both the Community Argo CD and GitOps Runtime's Argo CD.