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

Add Shared Resource CSI Driver to OCP Payload

    XMLWordPrintable

Details

    • Sprint 205, Sprint 207

    Description

      User Story

      As an OpenShift cluster admin
      I want official images for the Projected resource CSI driver
      So that I have fully certified and supported images for the projected resource CSI driver running on my cluster.

      Acceptance Criteria

      • Set up delivery pipeline for Projected Resource CSI driver via ART
      • Set up delivery pipeline for the Projected Resource CSI Driver operator via ART

      ART Checklist

      • Agree on the namings of the components
      • Align upstream naming of components (if possible and not done)
      • Ensure component has end to end CI testing upstream
      • Ensure OWNERS file has appropriate Bugzilla components
      • Create rhel-based Dockerfile that can be consumed by ART/OSBS
      • Create a build repository in Comet
      • Create a delivery repository in Comet
      • Request security audit from ProdSec
      • File build ticket with ART
      • Get images built in OSBS
      • After first build OSBS build add openshift release labels to Dockerfiles

      Notes

      Open questions:

      1. Will this ever be in the OCP payload? *YES*
      2. Does using CPaaS tie us to only install via OLM? Does it rule out our ability to install the driver via the OpenShift payload?

       

      We need to have CI configured in openshift/release before we begin adding images that will be managed by ART.

      Process is detailed in https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_wiki/guidelines_for_requesting_new_content_managed_by_ocp_art

      and

      https://source.redhat.com/groups/public/atomicopenshift/atomicopenshift_wiki/requesting_a_new_image_or_rpm_to_be_managed_by_art

      Things we will need set up:

      1. Listing in Comet
      2. Adding code to dist-git. Note - we won't need CI set up for dist-git, ART takes care of this with nightly releases and CI against the payload.
      3. Creating relevant Bugzilla components (or sub-components) - likely "Shared Resources CSI Driver" under Storage component
      4. OWNERS files validated and updated
      5. Submitting request to get ART

       

      Attachments

        Issue Links

          Activity

            People

              adkaplan@redhat.com Adam Kaplan
              adkaplan@redhat.com Adam Kaplan
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: