Undefined Openshift CI seems to be exhibiting flaky behavior more often in KAM
Tests observed as flaky:
1. Bringing the deployment infrastructure up
- login argocd API server - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-developer_kam/274/pull-ci-redhat-developer-kam-master-v4.8-integration-e2e/1440266266152538112
- application "dev-app-taxi" should be in "Synced" state - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-developer_kam/275/pull-ci-redhat-developer-kam-master-v4.8-integration-e2e/1440202992362983424
- application "cicd-app" should be in "Synced" state - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-developer_kam/275/pull-ci-redhat-developer-kam-master-v4.8-integration-e2e/1440181392880177152
- Then application "argo-app" should be in "Synced" state - https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/redhat-developer_kam/280/pull-ci-redhat-developer-kam-master-v4.8-integration-e2e/1440557559047000064
2. First CI run
Acceptance Criteria
CI jobs should pass without any errors