Merge pull request #35481 from lbscorpio/gitops

Fix case sensitive for Argo CD

Author: Preeticp

modules/gitops-creating-an-application-by-using-the-argo-cd-dashboard.adoc

@@ -16,12 +16,12 @@ endif::[]
 Argo CD provides a dashboard which allows you to create applications.
 
 ifdef::cluster[]
-This sample workflow walks you through the process of configuring Argo CD to recursively sync the content of the `cluster` directory to the `cluster-configs` application. The directory defines the {product-title} web console cluster configurations that add a link to the *Red Hat Developer Blog* under the {rh-app-icon} menu in the web console, and defines a namespace `spring-petclinic` on the cluster.
+This sample workflow walks you through the process of configuring Argo CD to recursively sync the content of the `cluster` directory to the `cluster-configs` application. The directory defines the {product-title} web console cluster configurations that add a link to the *Red Hat Developer Blog - Kubernetes* under the {rh-app-icon} menu in the web console, and defines a namespace `spring-petclinic` on the cluster.
 endif::cluster[]
 
 .Procedure
 
-. In the Argo CD dashboard, click the *New App* button to add a new Argo CD application.
+. In the Argo CD dashboard, click *NEW APP* to add a new Argo CD application.
 
 ifdef::cluster[]
 . For this workflow, create a *cluster-configs* application with the following configurations:
@@ -48,11 +48,10 @@ Revision:: `HEAD`
 Path:: `app`
 Destination:: `https://kubernetes.default.svc`
 Namespace:: `spring-petclinic`
-Directory Recurse:: `checked`
 endif::app[]
 
-. Click *Create* to create your application.
+. Click *CREATE* to create your application.
 
 . Open the *Administrator* perspective of the web console and navigate to *Administration* -> *Namespaces* in the menu on the left.
 
-. Search for and select the namespace, then enter `argocd.argoproj.io/managed-by=openshift-gitops` in the *Labels* field so that the Argo CD instance in the `openshift-gitops` namespace can manage your namespace.
+. Search for and select the namespace, then enter `argocd.argoproj.io/managed-by=openshift-gitops` in the *Label* field so that the Argo CD instance in the `openshift-gitops` namespace can manage your namespace.

modules/gitops-synchronizing-your-application-application-with-your-git-repository.adoc

@@ -8,11 +8,11 @@
 .Procedure
 . In the Argo CD dashboard, notice that the *cluster-configs* Argo CD application has the statuses *Missing* and *OutOfSync*. Because the application was configured with a manual sync policy, Argo CD does not sync it automatically.
 
-. Click the *Sync* button on the *cluster-configs* tile, review the changes, and then click *Synchronize*. Argo CD will detect any changes in the Git repository automatically. If the configurations are changed, Argo CD will change the status of the *cluster-configs* to *OutOfSync*. You can modify the synchronization policy for Argo CD to automatically apply changes from your Git repository to the cluster.
+. Click *SYNC* on the *cluster-configs* tile, review the changes, and then click *SYNCHRONIZE*. Argo CD will detect any changes in the Git repository automatically. If the configurations are changed, Argo CD will change the status of the *cluster-configs* to *OutOfSync*. You can modify the synchronization policy for Argo CD to automatically apply changes from your Git repository to the cluster.
 
 . Notice that the *cluster-configs* Argo CD application now has the statuses *Healthy* and *Synced*. Click the *cluster-configs* tile to check the details of the synchronized resources and their status on the cluster.
 
-. Navigate to the {product-title} web console and click {rh-app-icon} to verify that a link to the *Red Hat Developer Blog* is now present there. 
+. Navigate to the {product-title} web console and click {rh-app-icon} to verify that a link to the *Red Hat Developer Blog - Kubernetes* is now present there.
 
 . Navigate to the *Project* page and search for the `spring-petclinic` namespace to verify that it has been added to the cluster.
 +

modules/gitops-verifying-argo-cd-self-healing-behavior.adoc

@@ -33,4 +33,4 @@ $ oc scale deployment spring-petclinic --replicas 2  -n spring-petclinic
 ----
 .. In the {product-title} web console, notice that the deployment scales up to two pods and immediately scales down again to one pod. Argo CD detected a difference from the Git repository and auto-healed the application on the {product-title} cluster.
 
-. In the Argo CD dashboard, click the *app-spring-petclinic* tile → *App Details* → *Events*. The *Events* tab displays the following events: Argo CD detecting out of sync deployment resources on the cluster and then resyncing the Git repository to correct it.
+. In the Argo CD dashboard, click the *app-spring-petclinic* tile → *APP DETAILS* → *EVENTS*. The *EVENTS* tab displays the following events: Argo CD detecting out of sync deployment resources on the cluster and then resyncing the Git repository to correct it.

modules/logging-in-to-the-argo-cd-instance-by-using-your-openshift-credentials.adoc

@@ -14,7 +14,7 @@ Red Hat OpenShift GitOps Operator automatically creates a ready-to-use Argo CD i
 .Procedure
 
 . In the *Administrator* perspective of the web console, navigate to *Operators* -> *Installed Operators* to verify that the Red Hat OpenShift GitOps Operator is installed.
-. Navigate to the {rh-app-icon} menu -> *Application Stages* -> *Argo CD*. The login page of the Argo CD UI is displayed in a new window.
+. Navigate to the {rh-app-icon} menu -> *OpenShift GitOps* -> *Cluster Argo CD*. The login page of the Argo CD UI is displayed in a new window.
 . Obtain the password for the Argo CD instance:
 .. Navigate to the *Developer* perspective of the web console. A list of available projects is displayed.
 .. Navigate to the `openshift-gitops` project.