Owner: Architect:

Story (Required)

As an OpenShift user, I want to be able to bring my own clusters for testing purposes.

Background (Required)

In our current-implemented acceptance test runner, we spin up kind clusters ephemerally during the course of testing. This isn't a good reflection of how primaza's users will be using it - they're clusters are going to persist a lot longer than the tests are.

We should give users the opportunity to run our acceptance tests against their clusters as a check that their clusters are configured correctly. This will also save us a lot of time in CI, since we won't have to constantly restart the clusters we use to test.

Glossary

<List of new terms and definition used in this story>

Out of scope

Our acceptance tests shouldn't need to be modified for this to work. This should entirely be within the python backend. Furthermore, any bugs identified with the implementation should be filed and fixed separately from this.

The current scheme should also not be removed. We should have a way to indicate whether we want to use ephemeral clusters or provided clusters.

In Scope

Clusters should be provided to acceptance tests, not managed by them.

Approach(Required)

Within the acceptance tests, we have the idea of "clusters", which can either be a worker or primaza cluster. These environments will be implemented as namespaces within the provided clusters.

The clusters themselves should be provided as a set of administrative kubeconfig contexts. These will be passed onto the tests directly.

Finally, we'll also need to accept a way to have pre-built images. Implementation of this particular feature should be tracked in APPSVC-1294.

Demo requirements(Required)

Tests should be able to be run on provided clusters, which may not necessarily be kind clusters.

Dependencies

APPSVC-1294 will be necessary for this story's completion.

Acceptance Criteria

Development:

QE: Acceptance tests should be able to use provided k8s clusters for testing purposes.
QE: Acceptance tests should still be able to use ephemeral kind clusters for testing.
Documentation: Yes - provide documentation on how these clusters may be provided and how they are expected to be used.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied