Add new troubleshooting topic for GitOps apps (#768)

NimRegev · web-flow · commit 54bd32b220d9 · 2023-07-18T09:48:00.000+03:00
* Add new troubleshooting topic for GitOps apps

Added troubleshootin info for deployment in progressing state

* Update nav.yml

Added troubleshooting gitops apps entry to nav yaml

* Add screenshot for issue

* Update troubleshooting-gitops-apps.md

Implemented feedback comments

* Update troubleshooting-gitops-apps.md

Changed Possible Cause description

* Update troubleshooting-gitops-apps.md

Moved default behavior sentence up in Possible Cause
diff --git a/_data/nav.yml b/_data/nav.yml
@@ -366,6 +366,8 @@
           url: "/manage-application"
         - title: Progressive delivery with GitOps
           url: "/install-argo-rollouts"
+        - title: Troubleshooting GitOps applications
+          url: "/troubleshooting-gitops-apps"          
 
 
 
diff --git a/_docs/deployments/gitops/applications-dashboard.md b/_docs/deployments/gitops/applications-dashboard.md
@@ -198,10 +198,6 @@ The Quick View includes the following tabs:
 * Events: Displays status and sync events for the application.
 
 
-
-
-
-
 ## Monitor resources for selected application
 
 Monitor the resources deployed in the current version of the selected application in the Current State tab.  
@@ -510,6 +506,7 @@ You can:
 <!--* [Monitor updated resources by deployment](#monitor-updated-resources-by-deployment)  -->
 * [Monitor rollouts by deployment](#monitor-rollouts-by-deployment)
 
+See also [Troubleshooting GitOps applications]({{site.baseurl}}/docs/deployments/gitops/troubleshooting-gitops-apps/).
 
 **How to monitor deployments**
 1. If required, set filters to narrow the number of deployments for the selected application.
@@ -681,6 +678,7 @@ max-width="50%"
 %}
 
 
+
 ## Monitor services for selected application
 The Services tab shows the K8s services for each deployment of the application. 
 Each service shows the number of replicas, the endpoint IP, the labels that reference the application, and the health status.  
@@ -699,7 +697,8 @@ max-width="50%"
 
 ## Related articles
 [Creating GitOps applications]({{site.baseurl}}/docs/deployments/gitops/create-application)  
-[Managing GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application)  
+[Managing GitOps applications]({{site.baseurl}}/docs/deployments/gitops/manage-application) 
+[Troubleshooting GitOps applications]({{site.baseurl}}/docs/deployments/gitops/troubleshooting-gitops-apps)  
 [Home Dashboard]({{site.baseurl}}/docs/dashboards/home-dashboard)  
 [DORA metrics]({{site.baseurl}}/docs/dashboards/dora-metrics/)  
 
diff --git a/_docs/deployments/gitops/troubleshooting-gitops-apps.md b/_docs/deployments/gitops/troubleshooting-gitops-apps.md
@@ -0,0 +1,36 @@
+---
+title: "Troubleshooting GitOps applications"
+description: ""
+group: deployments
+sub_group: gitops
+toc: true
+---
+
+
+
+## Current release version stuck in Progessing state
+In the GitOps Apps dashboard, when viewing the Timeline tab for the selected application, the Current Version is shown as **Progressing**, though the application status is Healthy and Synced.
+
+{% include 
+	image.html 
+	lightbox="true" 
+	file="/images/troubleshooting/gitops-apps/timeline-current-version-progressing.png" 
+	url="/images/troubleshooting/gitops-apps/timeline-current-version-progressing.png" 
+	alt="Current version stuck in Progressing" 
+	caption="Current version stuck in Progressing"
+  max-width="60%" 
+%}
+
+### Possible Cause
+This issue can occur when Istio VirtualService and Argo Rollouts are used in your application in Codefresh.  
+The default behavior of VirtualService weights in Argo Rollouts can lead to synchronization issues with Git as the Rollout progresses.  
+For more information, see [Argo Rollouts with Istio](https://argoproj.github.io/argo-rollouts/features/traffic-management/istio/#istio){:target="\_blank"}.
+
+In Codefresh, this issue leads to a loop with the following behavior:
+* Current release remains as **Progressing** in the Timeline tab.
+* A new release when triggered, changes the previous release to **Terminated**, and the new release now remains stuck as **Progressing**.
+
+
+### Possible Actions
+
+To resolve this issue when using Istio with Argo Rollouts, configure the application following the best practices for [integration with GitOps](https://argoproj.github.io/argo-rollouts/features/traffic-management/istio/#integrating-with-gitops){:target="\_blank"} in the Argo Rollouts documentation.
diff --git a/images/troubleshooting/gitops-apps/timeline-current-version-progressing.png b/images/troubleshooting/gitops-apps/timeline-current-version-progressing.png
