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

Tech Preview Shared Resource CSI Driver

XMLWordPrintable

    • Tech Preview Shared Resource CSI Driver
    • BU Product Work
    • False
    • False
    • Done
    • OCPSTRAT-475 - Enable sharing ConfigMaps and Secrets across namespaces [Tech Preview]
    • OCPSTRAT-475Enable sharing ConfigMaps and Secrets across namespaces [Tech Preview]
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      * With this update, you can securely share `Secrets` and `ConfigMaps` objects across namespaces. This capability relies inline ephemeral volumes that are created by a new Shared Resource driver for Container Storage Interface (CSI), which is a Technology Preview feature. With this feature, workloads in one cluster namespace can consume `Secret` or `ConfigMap` objects in another namespace. (link:https://issues.redhat.com/browse/BUILD-293[BUILD-293])
      Show
      * With this update, you can securely share `Secrets` and `ConfigMaps` objects across namespaces. This capability relies inline ephemeral volumes that are created by a new Shared Resource driver for Container Storage Interface (CSI), which is a Technology Preview feature. With this feature, workloads in one cluster namespace can consume `Secret` or `ConfigMap` objects in another namespace. (link: https://issues.redhat.com/browse/BUILD-293 [ BUILD-293 ])

      OCP/Telco Definition of Done
      Epic Template descriptions and documentation.

      <--- Cut-n-Paste the entire contents of this description into your new Epic --->

      Epic Goal

      • Deliver the Projected Resources CSI driver via the OpenShift Payload

      Why is this important?

      • Projected resource shares will be a core feature of OpenShift. The share and CSI driver have multiple use cases that are important to users and cluster administrators.
      • The use of projected resources will be critical to distributing Simple Content Access (SCA) certificates to workloads, such as Deployments, DaemonSets, and OpenShift Builds.

      Scenarios

      As a developer using OpenShift
      I want to mount a Simple Content Access certificate into my build
      So that I can access RHEL content within a Docker strategy build.

      As a application developer or administrator
      I want to share credentials across namespaces
      So that I don't need to copy credentials to every workspace

      Acceptance Criteria

      • OCP conformance suite must ensure that the projected resource CSI driver is installed on every OpenShift deployment.
      • OCP build suite tests that projected resource CSI driver volumes can be added to builds. Only if builds support inline CSI volumes.
      • Release Technical Enablement - Docs and demos on how to create a Projected Resource share and add it as a volume to workloads. A special use case for adding RHEL entitlements to builds should be included.

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. …

      Open questions::

      1. …

      Done Checklist

      • CI - CI is running, tests are automated and merged.
      • Release Enablement <link to Feature Enablement Presentation>
      • DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
      • DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
      • DEV - Downstream build attached to advisory: <link to errata>
      • QE - Test plans in Polarion: <link or reference to Polarion>
      • QE - Automated tests merged: <link or reference to automated tests>
      • DOC - Downstream documentation merged: <link to meaningful PR>

              Unassigned Unassigned
              adkaplan@redhat.com Adam Kaplan
              Jitendar Singh Jitendar Singh
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: