Epic Goal

• ROSA / OSD consumes the Konflux built images that are released to the prod-service registry
• Improved regression testing. Every build gets deployed to Integration and
  • Triggers OSD E2E
  • Triggers Hive's QE regression testing
• Qualified progression through the different environments
  • After passing the aforementioned E2E and regression testing, the image progresses to staging and tests are run there again
• Scheduled, zero manual intervention promotion from stage to production

Why is this important?

• Reduce Hive QE & engineering cop duty toil
• Reduce Service Delivery & engineering testing toil
• Ensure all the regression tesing is run for the different environments
• Get the Konflux builds to Managed OpenShift production
• Leverage automated soaking time and roll out

Scenarios

1.  Merge queue in master:
   1. Prow gates that tests Hive. on-merge Konflux build
   2. crt-redhat-acm Hive Operator application's Release plan admission pushes to prod-service registry
   3. Hive's app-interface saas.yaml gets triggered and modifies the integration to the new prod-service build
   4. Trigger OSDE2E tests example from OSD
   5. Trigger Hive QE regression tests.
      1. On success, promote to stage
      2. Trigger OSDE2E SD tests
      3. Trigger Hive QE regression tests
         1. On success, the upcoming scheduled promotion to production can be made (weekly is fine)

Acceptance Criteria

• Automated roll outs to production
• Troubleshooting documented in SOP

Dependencies (internal and external)

1. app-interface
2. Konflux
3. Inscope
4. OpenShift prow CI

Previous Work (Optional):

1. https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/1337

Open questions::

1. How can we schedule the promotion to only happen when the stage regression testing succeeded?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Hive SOP describing the pipeline with troubleshooting steps <Link to sop>
• QE - tests run automated on deployment to env