Volumes Instead of Sidecars for the Artifact Repository

FEATURE REQUEST: Volumes Instead of Sidecars to upload/download data to the default Artifact Repository

Hi, I was wondering why Argo decided to use a sidecar to download/upload data to GCS/S3/etc when using the Default Artifact Repository.

Did we consider using the Volume abstraction in Kubernetes? It looks that there are types of volumes for many kinds of storage and that it would make it easy to add a new kind of storage for the Default Artifact Repository by implementing a new kind of volume.

https://ai.intel.com/kubernetes-volume-controller-kvc-data-management-tailored-for-machine-learning-workloads-in-kubernetes/

https://kubernetes.io/docs/concepts/storage/volumes/

Start by reading the current artifact repository behavior described in the issue, then review Kubernetes volume types and the linked Kubernetes Volume Controller article. Determine whether volumes can replace the sidecar approach for uploading and downloading data across the listed repositories. Done means a concrete, maintainable proposal or implementation path for the default artifact repository.

Written by the indexing model from the issue text.