As "a system engineer"
I want "better control of testruns"
So that "I can more properly manage the ETOS system."
Context
ETOS has become quite complex and we are seeing a lot of issues with regards to how we handle environments and the traceability of ETOS in general.
We should off-load some of this complexity to Kubernetes instead by writing an ETOS operator/controller. This way we could remove some complexity and implement it in the Reconcile loop of ETOS instead of having services deal with it themselves.
We can also more easily track faulty environments and testruns and make sure we release environments whenever a custom environment resource is deleted.
Summary
As "a system engineer" I want "better control of testruns" So that "I can more properly manage the ETOS system."
Context
ETOS has become quite complex and we are seeing a lot of issues with regards to how we handle environments and the traceability of ETOS in general. We should off-load some of this complexity to Kubernetes instead by writing an ETOS operator/controller. This way we could remove some complexity and implement it in the Reconcile loop of ETOS instead of having services deal with it themselves. We can also more easily track faulty environments and testruns and make sure we release environments whenever a custom environment resource is deleted.
Exemplification
No response
Drawbacks
No response
Out of Scope
No response
Further links
No response
Acceptance Criteria
No response
Implementation Ideas
No response