-
Task
-
Resolution: Done
-
Major
-
None
-
1
-
SECFLOWOTL-91 - OpenShift GitOps on ROSA
-
GITOPS Sprint 3247, GITOPS Sprint 3248, GITOPS Sprint 3250
Test ArgoCD UI Login as part of ROSA validation
Test Steps:
There are three approaches
I.
Try the logging in method by following Visualize your applications via the Argo CD UI section in https://spaces.redhat.com/pages/viewpage.action?spaceKey=GITOPS&title=KAM+and+DevConsole+end+to+end+Tests
II.
1. Install GitOps operator on your cluster
2. Navigate to Networking -> Routes in openshift-gitops project, click on the link that takes you to the ArgoCD UI page
3. Log In Via Openshift
III.
1. Remove dex configuration from ArgoCD CR and add extraConfig
$ oc -n openshift-gitops patch argocd openshift-gitops --type='json' -p='[{ "op": "add", "path": "/spec/extraConfig", "value":{ "oidc.tls.insecure.skip.verify": "true" } }, { "op": "add", "path": "/spec/sso", "value": { "keycloak": { "rootCA": "---BEGIN---END---" }, "provider": "keycloak" } }]'
2. Restart argocd server pod
$ oc rollout restart deployment.apps/openshift-gitops-server -n openshift-gitops
3. Wait for keycloak-1-deploy pod in openshift-gitops namespace to be Completed
4. Navigate to Networking -> Routes in openshift-gitops project and click on the link that takes you to the ArgoCD UI page
5. LOG IN VIA KEYCLOAK, Log in with openshift and follow the instructions
Acceptance Criteria:
- Login is tested with all three approaches
- Highest and lowest versions of supported OCP versions are covered
- clones
-
GITOPS-3311 [Test execution] - ArgoCD UI Login | AWS | ARM64
- Closed
- is cloned by
-
GITOPS-3476 [Test execution] - ArgoCD UI Login
- Closed
-
GITOPS-3491 [Test execution] - ArgoCD UI Login | OCP 4.12
- Closed