Story (Required)

As a customer trying to install Builds Operator in a disconnected cluster, I want to have the operator available & supported for Disconnected clusters.

Background (Required)

<Describes the context or background related to this story>

"Disconnected" clusters are those which do not have an outside connection to the Internet (also known as "air-gapped"). This means the cluster environment cannot download content directly from the Red Hat container registry. We need to determine how to build and release Builds for OpenShift so that customers can mirror the required content and install in their air-gapped environment

Out of scope

<Defines what is not included in this story>

• Mirror configuration at the cluster level
• Running builds in a disconnected environment
• Running builds behind a proxy.

Approach (Required)

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

• Reach out to other teams/groups that have configured an OLM operator for disconnected installation.
• Draft stories/action plan for supporting disconnected install:
  • Engineering tasks (related to operator, Konflux, etc.)
  • Documentation tasks
  • Quality Engineering tasks - how do we verify that it actually works?
  • Other tasks related to enablement and product security, if necessary

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

• Follow-up stories drafted in JIRA
• Spike identifies engineering tasks/requirements
• Spike identifies QE tasks/requirements, or gaps in our capabilities
• Spike identifies docs tasks/requirements
• Spike identifies tasks that require technical enablement for support engineers/field
• Spike identifies and changes needed for product security