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/installation/gitops/hybrid-gitops-helm-installation.md
+4-2Lines changed: 4 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -302,10 +302,12 @@ You can define one of three different access modes:
302
302
* Service-mesh-based, which requires explicitly disabling the tunnel- and ingress-based modes in the installation command. The service mesh may also need to be configured before and after installation. See[Ingress controller configuration](#ingress-controller-configuration) in this article.
303
303
304
304
305
-
**GitOps on cluster with existing Argo CD and Argo Rollouts**
305
+
306
+
**GitOps Runtime cluster with existing Argo CD**
306
307
*`fullnameOverride` configuration for resource conflicts
307
308
Installing the GitOps Runtime on the same cluster as Argo CD can cause conflicts when resources in both Community and Codefresh's Argo CD instances have the same name or attempt to control the same objects.
308
-
Customizing`fullnameOverride` values for Argo CD and Argo Rollouts in the GitOps Runtime's`values` file prevents these conflicts.
309
+
Customizing`fullnameOverride` values for Argo CD (and Argo Rollouts if installed) in the GitOps Runtime's`values` file prevents these conflicts.
310
+
309
311
310
312
* Resource tracking with`annotation`
311
313
Installing the GitOps Runtime on the same cluster as Argo CD requires that each Argo CD instance uses a different method to track resources. Using the same tracking method can result in conflicts when both instances have applications with the same names or when tracking the same resource. Setting the GitOps Runtime's Argo CD resource tracking to`annotation` prevents such conflicts.