Background

To be able to execute E2E tests, we need to be able to connect to the cluster and provide a client to our tests.

We also need tooling/scripts to be able run both the periodic and presubmit tests separately as well as generate junit reports.

Steps

• Set up an E2E test runner in Go that loads a kubernetes client
• Code should live in `test/e2e` in the CPMS repo
• Use ginkgo v2 labels to label tests as Periodic and/or Presubmit tests
• Set up a basic test that, on AWS checks that a CPMS exists and that it's status reports as expected, mark this test as both presubmit and periodic
• Set up a script that runs the E2E tests and configures JUnit output when appropriate, ensure the script can select the suite to run
• Set up make targets to run both the E2E suites (Periodic and Presubmit)

Stakeholders

• Cluster Infra

Definition of Done

• Basic test for CPMS presence on a fresh AWS cluster is merged
• Running the make targets for both presubmit and periodic executes this test against the cluster defined in `KUBECONFIG`

• Docs

• N/A

• Testing

• N/A