-
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
Add AWS overlay for production users #4337
Comments
/assign |
Jeffwan@9ae0464 |
FYI, there's a community maintained AWS overlay https://github.com/e2fyi/kubeflow-aws/tree/master/pipelines |
@Bobgy Yeah, I talked with @eterna2 in the past. I think we would like to leverage upstream base as more as possible. We will keep link to e2fyi as alternative. I know some users are already on it. At the same time, we will try to further simplify the setups and add cloud resources in the scope. for example, one CFN/ deploy manager to help setup aws resources |
Currently, platform-agnostic works well on AWS for user who like to experience KFP features. We(AWS) get some feedbacks users want to use more stable AWS services to replace some of the components in KFP. S3 and RDS start to be widely voiced.
I think pipeline team build good abstraction here, for example, GCP users can easily build minio-gcs-gateway and cloudsql proxy to override base manifest.
In AWS, we'd like to adopt similar solution, minio-s3-gateway is straighforward, however, RDS-proxy recently released is kind of complex to setup and it raise bar to setup KFP in production environment.
We probably like to plug RDS to KFP components directly if sql proxy is not that straightforward on AWS. There're some work already one in Kubeflow v1.0.x. Just create this issue to track our work on standalone manifest.
Please leave comments or suggestions and we can have more discussion.
/cc @PatrickXYS
The text was updated successfully, but these errors were encountered: