Story (Required)

As a developer trying to install Shipwright on my cluster I want Shipwright v0.13.0 operator version released and available on OperatorHub.io

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

We need to release the operator and make it available in our desired community operator catalogs:

• Upstream k8s operators (OperatorHub.io)
• Red Hat community operators (what appears in OCP OperatorHub)

Out of scope

<Defines what is not included in this story>

• Downstream operator release
• Changes to operator channel naming
• Blog/website updates upstream for operator release

Approach (Required)

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

• Run release GitHub action for operator.
• Publish operator bundle contents on the community operators repo.
• Publish operator bundle contents on the Red Hat community operators repo.

Bonus points if this process is documented and scripted.

Dependencies

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

• Operator deploys v0.13.0 of Shipwright Build.

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>

• Operator is released on GitHub
• Operator is available in the k8s community operators repo.
• Operator is available in the Red Hat community operators repo.

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