Epic Goal

To have the GitOps product onboarded to the Konflux platform and ready to release. 

Why is this important?

• All secure flow products should be onboarded and releasing through Konflux by the end of the year as per our organization goals. 
• CPaaS is being deprecated so we can't keep using it forever. 

Scenarios

1. ...

Acceptance Criteria (Mandatory)

• Have our own Konflux instance with all team members on-boarded to it
• Have all applications/components set up in Konflux with all necessary customizations made to them
• Have all secrets added correctly to push productized images to desired locations
• Have Konflux able to run integration tests to tell us when something goes wrong in the build
• Be able to release our product through the Konflux platform

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. KONFLUX-2308 

Open questions::

1. …

Done Checklist

• All team members are onboarded to our konflux instance: https://konflux.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/application-pipeline/access/workspaces/gitops 
• PR's to konflux release data with our desired configurations made and merged https://gitlab.cee.redhat.com/releng/konflux-release-data 
• We have an application in konflux for the gitops product that ships all our components (the same components that we already have in CPaaS should be the same in Konflux)
• Have a team meeting to discuss what specific customizations we want as a team (see child story on customizations for what we should discuss)
• PR made to our build pipeline that adds in customizations of point above
• Integration tests are able to run and successfully catch failures
• Complete a full test run of release process before moving over entirely from cpaas to konflux