Deploy RHOSO using Validated Patterns.
Make sure you don’t have any pending git commits in the repository
Validate the prerequisites
cd /home/lab-user/rhoso-gitops/
./pattern.sh make validate-prereq
./pattern.sh make show
Make sure the rendering of the Helm charts is successful
helm template charts/all/rhoso-gitops/ -f overrides/values-rhoso-gitops.yaml
Access the pattern Argo CD console to verify the deployment
Validated Patterns installs the RHOSO applications into the cluster (hub) Argo CD
instance in the openshift-gitops namespace. Use that console to watch child
applications such as operator-dependencies, openstack-operator, and
openstack-controlplane.
The AppProject name rhoso-gitops-standalone refers to the Validated
Patterns clusterGroup, not a separate Argo CD namespace. On this lab there is
no rhoso-gitops-standalone namespace and no standalone-gitops Argo CD
instance.
|
Extract the admin password:
argoPass=$(oc get secret/openshift-gitops-cluster -n openshift-gitops -o jsonpath='{.data.admin\.password}' | base64 -d)
echo $argoPass
Get the Route for the GitOps server:
argoURL=$(oc get route openshift-gitops-server -n openshift-gitops -o jsonpath='{.spec.host}{"\n"}')
echo $argoURL
Open https://$argoURL in a browser and log in as admin with the password
from the previous step.
Confirm the applications are syncing:
oc get applications -n openshift-gitops
If an application reports can not be managed when in namespaced mode, return
to the GitOps Operator cluster-scope prerequisite
and verify ARGOCD_CLUSTER_CONFIG_NAMESPACES includes openshift-gitops.