• As Partner/PSA/Consultant/Engineer I would like to run Conformance tests provided by OPCT in integrated platforms, So I can review custom installations without disrupting the execution, getting more accurate results.
• As a Partner I would like to install OpenShift in an cloud-provider VMware solution, like VMC(AWS), OCVS (Oracle), with platformType=vmware and run OPCT with default Conformance without disruption, so I can validate my custom installation on external environment.

DESCRIPTION

OPCT has been designed to run OpenShift and Kubernetes conformance e2e suites on OCP with a non-integrated platform (a.k.a agnostic installations/platform=None/External), following strictly the requirements of the Validation Program that it was created.

As OPCT is growing the adoption, and getting more visibility, the team used to receive questions about people trying to get familiar with OPCT, running in integrated providers, which is possible as our backend (openshift-tests binary) can determine which platform is running, selecting/skipping e2e tests for each one.

The challenge of running e2e in specific tests is that some prerequisites must be set before running the openshift-tests, like credentials for storage tests. More information here, how we are running on CI can be found on the setup script[1].

The goals of this card are:

• Identify which changes that need to be done on OPCT (mainly plugins) to run the openshift-tests correctly on a self-managed environment for platforms AWS and vSphere

ACCEPTANCE CRITERIA

• List of changes that need to be done to run OPCT in integrated platform AWS and vSphere
• Related cards were created describing the changes on OPCT to run OPCT on AWS and vSphere, isolated by platform

ENGINEERING REFERENCES

[1] Current script used on CI to setup cloud-provider specifics: https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh#L110-L174