-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
3
-
False
-
-
False
-
NEW
-
OBSDA-390 - Integration of Perses: backend & frontend / Internal Customers - OCP web console & RHACM console
-
NEW
-
-
-
Sprint 268
Background
The Perses operator was onboarded into COO. Operands should be also included in COO. In the case of Perses Operator. The Perses backend needs to be built and included in COO payload and image list in the operator CSV.
Outcome
- A new component, holding the Perses backend, is created in konflux COO
- A new git submodule pointing to Perses backend: https://github.com/perses/perses is created in konflux-coo
- A Dockerfile is created to build the perses backend in konflux-coo repo
- is cloned by
-
COO-704 On Board Perses backend component
-
- Closed
-
- mentioned on