As a user of test-operator:
I want to be able to update a configuration of an instance of test-operator related CR.

 
So that:
I can easily reconfigure running tests without the need to first delete the CR and then reapply it.
 
Definition of Done: 

• All test-operator CRs (Tempest, Tobiko, HorizonTest, AnsibleTest) can be easily reapplied with a different configuration.
• When a CR is reapplied with a different configuration then all the instances of test pods are deleted and new ones with the new configuration are created.

Constraints or Risks:

• If we delete a pod in the middle of tests execution it might happen that there are going to be uncleaned up test resources left. This can theoretically be prevented by only deleting the pods when they are already Completed and then starting the new ones.

Notes:
Right now when you want to update an existing instance of test-operator related CR the workflow looks something like this:

oc apply -f tempest.yaml
... tests pods are running ...
oc delete tempest --all
... test pods get deleted ...
oc apply -f tempest-modified.yaml
... new test pods are running ...

and we want it to simplify to:

oc apply -f tempest.yaml
... test pods are running ...
oc apply -f tempest-modified.yaml
# ^^ deletes old test pods and starts new ones with the new configuration