Story (Required)

As a cluster admin trying to use OpenShift Builds I want to be able to upgrade from v1.0 to v1.1 seamlessly

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

GA support requires seamless upgrades for y-stream and z-stream releases.

Out of scope

<Defines what is not included in this story>

• Install the Shared Resource CSI Driver via the OpenShift Builds operator
•  

Approach (Required)

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

• Verify whether it is possible to upgrade from 1.0 to 1.1 and ensure all the resource are deployed. 
• Create a Make target and the required scripts to test this end to end

Dependencies

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

• BUILD-720 (Shipwright operator as library)

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>

• OpenShift Builds operator can be upgraded from v2.0 to v2.1 via OLM
• Upgrade does not result in removal of Shipwright Builds if it was installed on the cluster.
• CI verifies upgrades remain functional so we do not regress.

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