Feature request
Add corev1.ImageVolumeSource as a supported volume source type in WorkspaceBinding, alongside the existing PVC, EmptyDir, ConfigMap, Secret, Projected, and CSI types.
This would allow users to mount container image filesystems as read-only workspace volumes in TaskRuns and PipelineRuns:
Use case
Kubernetes Image Volumes (ImageVolumeSource) allow mounting a container image's filesystem as a volume without running it as a container. This is useful for distributing tools, rpm cache, etc.
workspaces:
- name: my-tools
image:
reference: quay.io/example/my-tools:latest
pullPolicy: IfNotPresentCurrently, the only way to use image volumes with Tekton is through PodTemplate.Volumes
Feature request
Add corev1.ImageVolumeSource as a supported volume source type in WorkspaceBinding, alongside the existing PVC, EmptyDir, ConfigMap, Secret, Projected, and CSI types.
This would allow users to mount container image filesystems as read-only workspace volumes in TaskRuns and PipelineRuns:
Use case
Kubernetes Image Volumes (ImageVolumeSource) allow mounting a container image's filesystem as a volume without running it as a container. This is useful for distributing tools, rpm cache, etc.
Currently, the only way to use image volumes with Tekton is through PodTemplate.Volumes