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
When we have a VolumeOp component in a recurring-run pipeline the component creates new PVC every time a recurring run happens. However, In a use case where the subsequent runs should use the same PVC as the first run, the VolumeOp fails to handle this case.
Is there a workaround currently?
I understand we can create spec using V1PersistentVolumeClaim and pass it as k8s_resource argument but this seems to defeat the purpose of VolumeOp in the first place.
If this seems to be a useful feature I would be happy to create a PR.
Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.
The text was updated successfully, but these errors were encountered:
Feature Area
/area sdk
What feature would you like to see?
VolumeOp should allow re-using of existing PVC.
What is the use case or pain point?
When we have a VolumeOp component in a recurring-run pipeline the component creates new PVC every time a recurring run happens. However, In a use case where the subsequent runs should use the same PVC as the first run, the VolumeOp fails to handle this case.
Is there a workaround currently?
I understand we can create spec using
V1PersistentVolumeClaim
and pass it ask8s_resource
argument but this seems to defeat the purpose of VolumeOp in the first place.If this seems to be a useful feature I would be happy to create a PR.
Love this idea? Give it a 👍. We prioritize fulfilling features with the most 👍.
The text was updated successfully, but these errors were encountered: