You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By using projected volumes a user could pass an arbitrary amount of ConfigMaps or Secrets to a PipelineRun/TaskRun without modifying the actual Task/ClusterTask.
In kubevirt-tekton-tasks we have tasks to customize/sysprep VM images, where this would allow to pass data in a flexible way. The user could pass multiple ConfigMaps or Secrets to the task, which would also allow to split and reuse them in several tasks.
By adding support for projected volumes [1] as workspace type an
arbitrary amount of ConfigMaps or Secrets can be passed to a
TaskRun/PipelineRun without modifying the actual Task/ClusterTask.
This allows to pass data to Tasks/Pipelines in a flexible way.
Fixes#5075
[1] https://kubernetes.io/docs/concepts/storage/projected-volumes
Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>
Feature request
Support kubernetes projected volumes (https://kubernetes.io/docs/concepts/storage/projected-volumes/) as workspace type.
Use case
By using projected volumes a user could pass an arbitrary amount of ConfigMaps or Secrets to a PipelineRun/TaskRun without modifying the actual Task/ClusterTask.
In kubevirt-tekton-tasks we have tasks to customize/sysprep VM images, where this would allow to pass data in a flexible way. The user could pass multiple ConfigMaps or Secrets to the task, which would also allow to split and reuse them in several tasks.
The text was updated successfully, but these errors were encountered: