1. A Quickcluster cluster.

2. Use setup-nfs-quickcluster.sh to setup NFS.

1. Install the OpenShift GitOps Operator

oc create -f install-openshift-gitops-operator.yaml

Once the the operator installation is complete, the link to Argo CD will be visible from the OpenShift Console. Argo CD should be also accessible through this link: https://openshift-gitops-server-openshift-gitops.apps.[cluster_host]

Example for cluster_host: 'mycluster.lab.psi.pnq2.redhat.com'.
You can get the information from the Quickcluster cluster page.

1. Create the Argo CD logging app

oc create -f argocd-app.yaml

After a successful deployment, the sync indicator should indicate Synced and the overall health status of the app should be Healthy.

1. Apply the logging health checks

oc apply -f health-checks.yaml -n openshift-gitops

For example, clusterlogforwarder before applying the Argo CD health check:

clusterlogforwarder after applying the Argo CD health check:

1. Open Splunk in your browser with the following command:

xdg-open "$(oc get route splunk-web --template='{{.spec.host}}' --namespace=splunk)"

2. Login with u:admin/p:Password.
3. Run a Splunk query against the index rh_rhtap_dev_audit or rh_rhtap_dev_app.
   E.g: index="rh_rhtap_dev_audit"

Relevant pod logs can be found in the following namespaces:

1. Splunk dev image on Quay.io

1. OpenShift Logging
2. Deploy OpenShift Logging via CLI

1. external-secrets.io
2. Installing External Secrets Operator with OLM

1. Argo CD Operator
2. Argo CD

1. Red Hat OpenShift GitOps
2. Installing GitOps Operator

1. external-secrets operatorconfig fails to sync with the following error:

The Kubernetes API could not find operator.external-secrets.io/OperatorConfig for
requested resource external-secrets/cluster. Make sure the "OperatorConfig" CRD is
installed on the destination cluster.

How to resolve:

1. Terminate the current sync attempt.
2. sync the external-secrets namespace.
3. sync the external-secrets-operator
4. Everything else should sync successfully.