Uploaded image for project: 'OpenShift Builds'
  1. OpenShift Builds
  2. BUILD-1141

Indicate Operator is Proxy-Aware

XMLWordPrintable

    • 2
    • False
    • None
    • False
    • SECFLOWOTL-28 - Openshift Builds in clusters with restricted networks
    • Enhancement
    • Builds Sprint #16

      Story (Required)

      As a cluster admin trying to deploy Builds for OpenShift in a proxied cluster I want the Builds operator to indicate it can be supported on my cluster.

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

      Red Hat OLM operators can add "infrastructure annotations" to their CSVs, to report that the operators can take advantage of specific OpenShift features. `proxy-aware` is one of them.

      See OLM infrastructure annotations for more info.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      • Add the "proxy-aware" annotation
      • Verify this functionality using cluster-bot provisioned

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

      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

              rh-ee-asatyam Ayush Satyam
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: