Feature Overview (aka. Goal Summary)  

Improve the level of automation in delivery the Hive Operator images to managed OpenShift

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

• 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

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

• The entire pipeline is automated
• The progress of builds through the pipeline can be monitored
• Manual delivery continues to be possible to deal with incidents

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Hive Operator delivery to managed OpenShift services

Out of Scope

Self-managed Hive

Background

Hive is currently already built in Konflux as part of the crt-redhat-acm workspace.

Its builds are also pushed to the prod-service registry thanks to the ReleaseAdmissionPlan introduced in https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/1337

Customer Considerations

Hive Operator rollouts must not negatively impact SLOs nor affect cluster creation API availability.

Documentation Considerations

There should be thorough documentation of the end state in hive-sops

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

Impacts ROSA / OSD. ARO might want to follow-up

Builds should be mirrored automatically to Operator Hub when they promote to production