Goal

As a developer, I want to add Kubernetes volumes to any Shipwright build
So that I can provide content in Secrets, ConfigMaps, and Persistent Volumes into my build.

Problem

WIP
This is a follow up from BUILD-9

Develop
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