Integrate Konflux for CI/CD.

Outline

1. On-boarding: open a tracker ticket at the konflux project, choose a konflux instance, set up a workspace, a tenant and a konflux app
2. Access: set up permissions and roles via the konflux data repository
3. Build: in the konflux app, create konflux component(s) that will generate pipeline configurations in your code-repository, and have konflux run on PRs and long-lived branches (e.g. 'main') and build onto quay
4. Build verification: add unit tests, linting, etc. to the build pipelines
5. Integration tests: in our konflux app, set up integration tests to drive E2E verification (basic ones are mandatory, but custom tests like our cypress E2E suites are optional for the migration, and can be handled later)
6. Release: move quay images into a stable konflux image-repository (dedicated for prod') and hook them up to live deployments
7. Clean up: get rid of any redundancies, i.e. jenkins jobs/templates in app-interface, hook scripts in the source repo (e.g. build_deploy.sh), etc.

Notes

• FedRAMP teams will own the migration for in-boundary environments (and the security-compliance branch). Their builds will be defined via a separate Konflux component (call it "uhc-portal-sc"), with the docker-build-oci-ta pipeline (instead of docker-build)

References

• Official Konflux docs
• On-boarding process guide on ConsoleDot docs
• Konflux migration dashboard user guide
• Konflux Migration Images spreadsheet