Goal

As a developer, I want to add Kubernetes volumes to Shipwright build strategies
So that build strategy authors can share content between build steps, read configuration from the cluster, and cache content in persistent locations.

Problem

Build strategy authors do not have a means configuring volumes in their build steps.
This has forced steps to be "squashed" so content can be shared across processes.
It also prevents strategies from inferring configuration from the cluster and storing cached content in persistent volumes.

Why is this important?
This will unlock the ability of build strategies to use cached content (ex - image cache on the node).

Dependencies

• Tekton Workspaces

Prioritized epics + deliverables (in scope / not in scope)

• R&D use workspaces to cache dependencies
• Volume mounts in Shipwright Builds

Estimate (XS, S, M, L, XL, XXL):

Previous Work:
NA

Open Questions:
NA