Story (Required)

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

As a cluster admin trying to deploy Builds for OpenShift in an air-gapped environment I want the builds operator Cluster Service Version (CSV) to have all metadata needed for air-gapped install.

Background (Required)

<Describes the context or background related to this story>

OLM (v0.Y) operators declare all their metadata in the ClusterServiceVersion object, which is included in the OLM bundle. To support air-gapped install, all container images referenced by the product need to be referenced by digest in the CSV relatedImages stanza.

See OLM restricted networks doc and OLM Infrastructure CSV Annotations

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

Dependencies

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

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

• CSV within the OLM bundle contains related images for all components:
  • Shipwright Build images, including validating admission webhooks
  • Shared Resource CSI Driver images, including validating admission webhooks
  • Builds for OpenShift operator
  • Images referenced in build strategies deployed by the operator
• All images in the CSV related images reference by digest. (:tag@sha digests allowed)
• All operand deployments reference images by digest
• All deployed build strategies reference images by digest
• Operator CSV declares that it supports disconnected install by adding the `features.operators.openshift.io/disconnected: "true"` annotation

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