Details
Normal Description
This is for the upstream argocd.
ArgoCD E2E can be executed in a remote way. In fact, that is the approach that we follow in the GitOps QE team since there is no possibility to run local E2E tests for ArgoCD with the release candidate, as it has to be installed in a production-ready OCP cluster.
The problem is that the documentation is completely outdated, and when you follow it to try to configure a system from scratch, capable of running remote tests (in our case, a container image to run within tekton pipelines) you realize that it doesn't work for some reason, maybe because of the outdated information, or maybe because of some gaps in that documentation.
Currently, this is how you can run e2e tests against the workloads (argocd deployed).
https://github.com/argoproj/argo-cd/blob/master/test/remote/README.md
Acceptance Criteria:
- To design a working ArgoCD E2E remote method to propose in the upstream contributor meeting.
- To open a PR against the upstream project, so all the community can benefit from this update.