-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python DSL should support multiple storage options (GCS, PVC, etc.) #275
Comments
I think this should mostly be managed on the backend side and be transparent to the containers/components. See https://github.com/argoproj/argo/blob/master/ARTIFACT_REPO.md |
The argo is limited to s3 compatible storage. Pipeline component should support arbitrary store. E.g. accessing HDFS. |
vicaire
changed the title
Python DSK should support multiple storage options (GCS, PVC, etc.)
Python DSL should support multiple storage options (GCS, PVC, etc.)
Mar 27, 2019
Resolving in favor of #801 |
magdalenakuhn17
pushed a commit
to magdalenakuhn17/pipelines
that referenced
this issue
Oct 22, 2023
HumairAK
pushed a commit
to red-hat-data-services/data-science-pipelines
that referenced
this issue
Mar 11, 2024
…i-user (kubeflow#275) * move website instructions and optimize it for kfp-tekton, also update kfp user guide for multi-user * Apply suggestions from code review Co-authored-by: Andrew Butler <Andrew.Butler@ibm.com> * fix few grammar on the original website docs * update single user kfdef to a staging build * explicit the supported k8s version * Apply suggestions from code review Co-authored-by: Animesh Singh <singhan@us.ibm.com> * Apply suggestions from code review Co-authored-by: Animesh Singh <singhan@us.ibm.com> * Update developer_guide.md Co-authored-by: Animesh Singh <singhan@us.ibm.com> Co-authored-by: Andrew Butler <Andrew.Butler@ibm.com> Co-authored-by: Animesh Singh <singhan@us.ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: