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: content/patterns/medical-diagnosis/getting-started.adoc
+5-34Lines changed: 5 additions & 34 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -376,7 +376,7 @@ A pop-up error with the message "Oh no! Something went wrong." might appear duri
376
376
377
377
The {rh-gitops} Operator displays in list of *Installed Operators*. The {rh-gitops} Operator installs the remaining assets and artifacts for this pattern. To view the installation of these assets and artifacts, such as {rh-rhacm-first}, ensure that you switch to *Project:All Projects*.
378
378
379
-
Wait some time for everything to deploy. You can track the progress through the `Hub ArgoCD` UI from the nines menu. The `something` project appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
379
+
Wait some time for everything to deploy. You can track the progress through the `Hub ArgoCD` UI from the nines menu. The `xraylab-database` project appears stuck in a `Degraded` state. This is the expected behavior when installing using the OpenShift Container Platform console.
380
380
381
381
* To resolve this you need to run the following to load the secrets into the vault:
382
382
+
@@ -427,8 +427,8 @@ $ ./pattern.sh make install
427
427
428
428
. Verify that the Operators have been installed.
429
429
.. To verify, in the OpenShift Container Platform web console, navigate to *Operators → Installed Operators* page.
430
-
.. Check that the Operator is installed in the `openshift-operators` namespace and its status is `Succeeded`.
431
-
. Verify that all applications are synchronized. Under the project `yada-yada-hub` click the URL for the `hub` gitops `server`. The Vault application is not synched.
430
+
.. Check that the *Red Hat OpenShift GitOps Operator* is installed in the `openshift-operators` namespace and its status is `Succeeded`.
431
+
. Wait some time for everything to deploy. You can track the progress through the `Hub ArgoCD` UI from the nines menu.
@@ -440,36 +440,7 @@ For more information, see section on https://validatedpatterns.io/secrets/vault/
440
440
441
441
To check the various applications that are being deployed, you can view the progress of the {rh-gitops-short} Operator.
442
442
443
-
. Obtain the ArgoCD URLs and passwords.
444
-
+
445
-
The URLs and login credentials for ArgoCD change depending on the pattern name and the site names they control. Follow the instructions below to find them, however you choose to deploy the pattern.
446
-
+
447
-
Display the fully qualified domain names, and matching login credentials, for
448
-
all ArgoCD instances:
449
-
+
450
-
[source,terminal]
451
-
----
452
-
ARGO_CMD=`oc get secrets -A -o jsonpath='{range .items[*]}{"oc get -n "}{.metadata.namespace}{" routes; oc -n "}{.metadata.namespace}{" extract secrets/"}{.metadata.name}{" --to=-\\n"}{end}' | grep gitops-cluster`
453
-
CMD=`echo $ARGO_CMD | sed 's|- oc|-;oc|g'`
454
-
eval $CMD
455
-
----
456
-
+
457
-
.Example output
458
-
+
459
-
[source,text]
460
-
----
461
-
NAME HOST/PORT PATH SERVICES PORT TERMINATION WILDCARD
Examine the `medical-diagnosis-hub` ArgoCD instance. You can track all the applications for the pattern in this instance.
@@ -486,7 +457,7 @@ Examine the `medical-diagnosis-hub` ArgoCD instance. You can track all the appli
486
457
487
458
. Accept the SSL certificates on the browser for the dashboard. In the {ocp} web console, go to the Routes for project `openshift-storage``. Click the URL for the `s3-rgw`.
0 commit comments