Story (Required)

As a user trying to start a pipeline from the OpenShift console I want the system to choose a storage class when choosing a VolumeClaimTemplate for the shared-workspace

Background (Required)

When considering the form for triggering a pipeline (creating a pipeline run) as a front-end for a complex process that runs behind the scenes, we'd want the aforementioned form to be as simple as we can. By allowing users not to think about the chosen storage class (but still being able to chose it when needed) we can make the form simpler for end-users

Approach (Required)

I think the default value for the storage class needs to be something like "choose automatically" and when that option is picked, the storage class property would not be set on the PVC, resulting in the system picking up an arbitrary storage class that can provide a volume

Acceptance Criteria (Mandatory)

Start a pipeline from the OpenShift console and do not change the value of the storage class property. As a result, a volume will be provisioned on one of the storage classes defined in the system and the pipeline run would start.

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