Gitops byoa limitations (#1298)

* Add BYOA limitations table

* Update runtime-install-with-existing-argo-cd.md

* Update runtime-install-with-existing-argo-cd.md

Removed limitation on multisource apps

* Update runtime-install-with-existing-argo-cd.md

* Update runtime-install-with-existing-argo-cd.md

* Update runtime-install-with-existing-argo-cd.md

Author: NimRegev

_docs/deployments/gitops/manage-application.md

@@ -707,8 +707,13 @@ Rename an Application Set and point all existing applications to the renamed App
 %}
 
 ## Enable precise sync detection for monorepo apps
-Enable the ACR Controller in GitOps Runtimes to precisely detect sync operations that triggered deployments for applications in monorepo setups.
+Enable the ACR (Application Change Revision) Controller in GitOps Runtimes to precisely detect sync operations that triggered deployments for applications in monorepo setups.
 
+>**NOTE**  
+Not supported for GitOps Runtime installations with existing Argo CD. 
+
+
+ACR Controller 
 When enabled, the ACR Controller:
 * Identifies and tracks application-specific changes by analyzing the application’s source path.
 * Compares revisions to identify the specific sync operation that triggered the promotion or deployment.

_docs/deployments/gitops/monitor-applications.md

@@ -314,8 +314,10 @@ Use the `IgnoreExtraneous` filter to hide generated resources such as `ConfigMap
 
  The application remains in-sync even when such resources are syncing or out-of-sync.  
 [Argo CD](https://argo-cd.readthedocs.io/en/stable/user-guide/compare-options){:target="\_blank"}
+
 >**NOTE**  
-The `IgnoreExtraneous` filter when applied only affects sync status.  
+The `IgnoreExtraneous` filter is disabled for Runtime installations with existing Argo CD instances.   
+When applied, the `IgnoreExtraneous` filter only affects sync status.  
 Degraded resources impact the health status of the application.
 
 ##### Add `IgnoreExtraneous` annotation

_docs/deployments/gitops/troubleshooting-gitops-apps.md

@@ -76,3 +76,17 @@ time="2024-10-15T18:35:54Z" level=info msg="Patch operation sync result for appl
 1. Send the logs collected to the Support team for further investigation.
 
 
+## Filter by Kubernetes labels in Current State is disabled
+
+### Possible Causes
+You have installed the GitOps Runtime with an existing Argo CD instance.  
+This filter option in the Current State tab is currently not supported.  
+
+Stay tuned for updates on this feature.
+
+## Ignore Extraneous filter in the Current State tab is disabled
+
+### Possible Causes
+You have installed the GitOps Runtime with an existing Argo CD instance.  
+This filter option in the Current State tab is currently not supported.  
+

_docs/installation/gitops/runtime-architecture.md

@@ -223,8 +223,9 @@ In monorepo environments where multiple applications share a single repository,
 * Ensures that notifications are scoped to the application that was actually modified, preventing unnecessary notifications for other applications within the same repository, improving clarity and reducing noise.
 
 >**NOTE**  
-  The ACR Controller is supported from Runtime version 0.13.0 and higher.   
-  It does not support multi-source applications.
+  The ACR Controller is supported from Runtime version 0.13.0 and higher for GitOps Runtime installations with new Argo CD. Not supported for installations with existing Argo CD.   
+  It does not support multi-source applications.  
+
 
 ##### Configuration
 

_docs/installation/gitops/runtime-install-with-existing-argo-cd.md

@@ -9,7 +9,10 @@ toc: true
 ## GitOps Runtime with existing Argo CD
 This article describes how to install GitOps Runtimes in a Codefresh account using a Helm chart on a _cluster that already has an Argo CD instance_.
 
-This option allows you to install the GitOps Runtime without deploying a new Argo CD instance. Instead, you _install the GitOps Runtime in the same namespace as the existing Argo CD instance_. The Runtime authenticates with the Argo CD instance through the [Argo CD Admin API token]({{site.baseurl}}/docs/installation/gitops/runtime-argocd-admin-api-token/) which you need to provide, and connects to key Argo CD services.
+This option allows you to install the GitOps Runtime without deploying a new Argo CD instance. Instead, you _install the GitOps Runtime in the same namespace as the existing Argo CD instance_. The Runtime authenticates with the Argo CD instance through the [Argo CD Admin API token]({{site.baseurl}}/docs/installation/gitops/runtime-argocd-admin-api-token/) which you need to provide, and connects to key Argo CD services. See also [notes on behavior for Runtimes with existing Argo CD](#gitops-runtime-with-existing-argo-cd-behavior).
+
+To install the _GitOps Runtime with a new Argo CD instance_, see [Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).
+
 
 <iframe width="560" height="315" src="https://www.youtube.com/embed/vtCoi3-Rt6w?si=EqlKsiRtdIGcZLaX" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
 
@@ -18,16 +21,13 @@ The Codefresh `values.yaml` available [here](https://github.com/codefresh-io/git
 Review how Codefresh [validates the Runtime's values.yaml]({{site.baseurl}}/docs/installation/gitops/gitops-values-yaml-validation/).
 
 
-To install the GitOps Runtime with a new Argo CD instance, see [Install GitOps Runtime with new Argo CD]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/).
 
 ## Before you begin
 * Make sure you meet the [minimum requirements]({{site.baseurl}}/docs/installation/gitops/runtime-system-requirements/) for installation
 * Verify that you complete all the [prerequisites]({{site.baseurl}}/docs/installation/gitops/runtime-prerequisites/)
 * Verify you have a [valid Argo CD Admin API token]({{site.baseurl}}/docs/installation/gitops/runtime-argocd-admin-api-token/)
 
 
-
-
 ## Step 1: Select Runtime install option
 
 1. On the Getting Started page, click **Install Runtime**.
@@ -242,6 +242,23 @@ Depending on your configuration, if you have private registries, you need to ove
 By default, the GitOps Runtime can deploy to the cluster it is installed on. You can add [Git Sources]({{site.baseurl}}/docs/installation/gitops/git-sources/), use [Terraform to connect external clusters]({{site.baseurl}}/docs/installation/gitops/managed-cluster/#add-a-managed-cluster-with-terraform), and [create and deploy Argo CD applications]({{site.baseurl}}/docs/deployments/gitops/create-application/).
 
 
+
+## GitOps Runtime with existing Argo CD behavior
+
+The table below outlines the differences in features and functionality when using GitOps Cloud with an existing (bring your own) Argo CD installation, compared to a new Argo CD (forked) installation.
+
+{: .table .table-bordered .table-hover}
+| **Feature/Functionality**|  **Behavior for existing Argo CD installation**   |
+| --------------        | ---------------- |
+|**Multiple GitOps Runtimes and Argo CD instances on same cluster** | Not supported. <br>Multiple GitOps Runtimes and Argo CD instances when separated by namespaces on the same cluster is not supported.  |
+| **Sync detection for monorepo apps** | Not supported. <br> The Application Change Revision (ACR) Controller which enables precise and accurate sync detections for applications from mono repositories is not supported. When using mono repos for applications with an existing Argo CD instance, this means that notifications may not be aligned with the precise sync operations that triggered syncs for deployments. For details, see [Application Change Revision Controller]({{site.baseurl}}/docs/installation/gitops/runtime-architecture/). |
+| **Application source and destination URL validations** | Not supported. <br>When creating new Argo CD applications from the Codefresh UI, GitOps Cloud does not validate the Source and Destination URLs configured for the application. This means that incorrect URLs are saved and may cause application sync or deployment failures.<br>_Update pending_. |
+|**Filter application resources by label** | Not supported. <br>The filter by **Kubernetes labels** in More Filters in the Current State tab is disabled. <br>_Update pending_. |
+|**Filter application by extraneous resources** | Not supported.<br> The **Ignore Extraneous** button in the Current State tab is disabled. |
+
+
+
+
 ## Related articles
 [Configuring GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/runtime-configuration/)  
 [Upgrading GitOps Runtimes]({{site.baseurl}}/docs/installation/gitops/manage-runtimes/#upgrade-gitops-runtimes/)