Story (Required)

As a Red Hat engineer trying to release Builds for OpenShift I want to release the operator with Konflux.

<Describes high level purpose and goal for this story. Answers the questions: Who is impacted, what is it and why do we need it? How does it improve the customer’s experience?>

Background (Required)

<Describes the context or background related to this story>

For Builds 1.1, we are going to build and release the operator with Konflux

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

• Create ReleasePlanAdmission object for operator in Konflux
  Release plans are stored in the following repo. https://gitlab.cee.redhat.com/releng/rhtap-release-data
  Instructions: https://gitlab.cee.redhat.com/releng/rhtap-release-data/-/blob/main/README.md?ref_type=heads
• Get access to managed workspace
• Update Policy in the Integration Test
• Create ReleasePlan object
• Trigger Release

Refer to doc:

https://gitlab.cee.redhat.com/konflux/docs/users

https://redhat-appstudio.github.io/docs.appstudio.io/Documentation/main/how-to-guides/con_release_application/

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

• All operator components onboarded to Konflux

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

• OLM bundle is able to be built
• ReleasePlanAdmission object is created and submitted to Product Security for review.
• Integration test for operator updated to ensure compliance with RPA
• ReleasePlan created and release triggered
•  

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met