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

Deploy Shared Resources via OpenShift Builds Operator

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • builds-1.1
    • builds-1.1
    • shared-resources
    • None
    • 8
    • False
    • None
    • False
    • SECFLOWOTL-27 - Shared Resource CSI Driver GA
    • Builds Sprint #7, Builds Sprint #8, Builds Sprint #9

      Story (Required)

      As a cluster admin trying to use the Shared Resource CSI Driver I want the operator to deploy the Shared Resource CSI driver via an API.

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

      After the issues deploying the driver on OCP 4.13, we have pivoted and will be deploying the Shared Resource CSI driver via the OpenShift Builds operator.

      Out of scope

      <Defines what is not included in this story>

      • Re-productize the Shared Resource CSI driver images (see SRCD-5)
      • Produce an operator that includes the re-productized CSI driver images downstream.
      • Integration testing - deferred to our quality epic for Builds 1.2
      • Cleanup behavior if the OpenShiftBuild CR is deleted or the operator itself is uninstalled.

      Approach (Required)

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

      • Add code in the operator to install Shared resources CSI driver components images (webhook, CRDs, CSI driver).
        • Use Manifestival and the manifests in openshift/csi-driver-shared-resource-operator
        • Apply appropriate transformations to set the namespace and image references (if necessary). Namespace should be the same as where the operator is deployed ("openshift-builds")
      • Reconcile on any changes in the CSI drivers resources.
      • Manual verification once we have the operator bundle built and can test e2e.

      Dependencies

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

      • BUILD-719 (Bootstrap OpenShift Builds operator)

      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>

      • OpenShift Builds operator can deploy the Shared Resource CSI driver using images built on Konflux.
      • Demo/verify manually that when the builds operator is installed, the Shared Resource CSI driver is deployed in the openshift-builds namespace.

      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-apjagtap Apoorva Jagtap
              adkaplan@redhat.com Adam Kaplan
              Jitendar Singh Jitendar Singh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: