Story (Required)

As a cluster admin trying to install the Shared Resource CSI driver I want the official OpenShift Builds operator to deploy and manage the Shared Resource CSI driver components.

<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>

This is the culmination of SRCD-4 and SRCD-5 - deploying the Shared Resource CSI driver via the OpenShift builds operator

Out of scope

<Defines what is not included in this story>

TBD

Approach (Required)

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

TBD from refinement

Dependencies

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

• BUILD-722
• SRCD-5

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>

• Release candidate of the OpenShift Builds operator is able to deploy both Shipwright Builds and the Shared Resource CSI Driver
• CI and QE testing of the operator passes

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