During the development of the test-operator we introduced a duplicate code that can be easily abstracted away. Let's identify this duplicate code and let's modify the code of the test-operator so that we have all the common code in one place.

Ideally, once this ticket is resolved, we have a simple template (or set of steps) that one can follow when introducing a new custom resource into the test-operator. One can just copy this template and add an additional logic that differs from the rest of the test-operator.

This will also simplify any bug fixes in the future. For example, if we discover a bug that is related to all custom resources then we can just modify the common portion of the code.

DoD:

• We abstracted away all the duplicate code in the test-operator.
• If there is a bug that is related to all custom resource managed by the test-operator then if we fix the issue on one place it would then be fixed for all custom resources.