Story (Required)

As a Kubernetes cluster administrator
 I want to have a set of installed cluster strategies when i install the shipwright operator
 So that developers can start using shipwright builds without any further manual steps

As a Kubernetes cluster administrator
 I want to be able to provide an url of manifest file and install my own catalog of Shipwright Builds Strategies via the Shipwright Operator
 So that I can provide a custom subset of Shipwright Build Strategies to my developers

As a Kubernetes cluster administrator
 I want to be able to install a custom ociArtifact of Shipwright Builds Strategies via the Shipwright Operator
 So that I can provide a custom subset of Shipwright Build Strategies to my developers

Background (Required)

Actually with the Shipwright operator, the user installs the Shipwright Build Controller. 
 Installation and upgrade of Build Strategies and Cluster Strategies is currently a manual process
 In order to improve user experience around Shipwright, the Shipwright Operator should also install the build strategies.

Out of scope

 - Add a new operator to install the Build Strategy catalog
 - Curate or rework the Build Strategies in the upstream build repository when copied to the new catalog repository

Approach (Required)

Add SHIP to community repo

Dependencies

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

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>

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