-
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
[feature] Allow manifests to set external Object Store to deploy Kubeflow Pipelines #10651
Comments
Hi @rimolive , I spent alot of time on this yesterday and probably will continue working on this during this week, if i get it to work i will update you. Below are my findings so far: pipeline logs:
workflow controller pod logs:
" I tried to create artifact-repositories configmap manually but also didnot work" content of : workflow-controller-configmap
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Feature Area
What feature would you like to see?
Following this Slack thread about using an external minio, users should be able to deploy kfp using an external Object Store instance.
What is the use case or pain point?
Manifests are tied to the bundled minio instance, which is very old, and does not fulfill the users requirements for a secure kfp installation
Is there a workaround currently?
It is possible to either tweak the manifests or configure manually each kfp Deployment to point to an external objStore, but it is undocumented and even experienced users wouldn't be able to do this without spending a lot of time and effort.
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: