Background 

We must create a testing ground for adding a new component in konflux before it add it to the cluster observability operator's release application. This is important because it prevents us from breaking the current COO release. We can modify and test components before we add them to the release application. 

Konflux has a concept of applications and components. One application can contain many components. The cluster observability operator application in Konflux has many components, one of which will be the perse-operator.  

Outcome

• A staging application in Konflux that tests the build configuration of new components 

Steps

1. Create new repository to house the component configuration 
   1. will put in observability-ui/konflux-coo-dev for now 
2. Create the component configurations 
   1. git submodule of perses-operator that points to main
   2. create Dockerfile.perses-operator that instructs the Konflux pipeline to how to build the component 
3. Onboard a new application to Konflux 
   1. Used Konflux UI
   2. Add secrets for base images from brew.registry.redhat.io and registry.redhat.io
   3. Create PR on observability-ui/konflux-coo-dev, this triggers Konflux to run its CI/CD pipeline
4. See if the build succeeds, then we can make a pull request in the actual repository that houses the configuration for COO releases (rhobs/konflux-coo) (e.g. OU-453)