Merge pull request #58045 from masauso-lungu/ML-RHDEVDOCS-2857

ML-RHDEVDOCS-2857: Added a step to verify that all components were installed

Author: abrennan89

modules/op-installing-pipelines-operator-in-web-console.adoc

@@ -57,3 +57,44 @@ The Operator is installed automatically into the `openshift-operators` namespace
 ====
 +
 . Verify that the *Status* is set to *Succeeded Up to date*  to confirm successful installation of {pipelines-title} Operator.
++
+[WARNING]
+====
+The success status may show as *Succeeded Up to date* even if installation of other components is in-progress. Therefore, it is important to verify the installation manually in the terminal.
+====
++
+. Verify that all components of the {pipelines-title} Operator were installed successfully. Login to the cluster on the terminal, and run the following command:
++
+
+[source,terminal]
+----
+$ oc get tektonconfig config
+----
++
+.Example output
+----
+NAME     VERSION   READY   REASON
+config   1.9.2     True 
+----
++
+If the *READY* condition is *True*, the Operator and its components have been installed successfully.
++
+Additonally, check the components' versions by running the following command:
++
+[source,terminal]
+----
+$ oc get tektonpipeline,tektontrigger,tektonaddon,pac
+----
++
+.Example output
+----
+NAME                                          VERSION   READY   REASON
+tektonpipeline.operator.tekton.dev/pipeline   v0.41.1   True 
+NAME                                        VERSION   READY   REASON
+tektontrigger.operator.tekton.dev/trigger   v0.22.2   True    
+NAME                                    VERSION   READY   REASON
+tektonaddon.operator.tekton.dev/addon   1.9.2     True 
+NAME                                                             VERSION   READY   REASON
+openshiftpipelinesascode.operator.tekton.dev/pipelines-as-code   v0.15.5   True 
+----
+