-
Notifications
You must be signed in to change notification settings - Fork 791
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
Update Pipelines standalone deployment to describe generic standalone (as well as GCP) #1253
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
/assign |
From a discussion today: The standalone deployment guide currently describes a GCP-specific deployment. But only one part of the guide is GCP-specific (the inverting proxy) and the rest can be generic to allow deployment on another clouds e.g. AWS. We should update the page so that it describes the generic deployment of Pipelines Standalone, with a GCP-specific section and guidelines for how other clouds/on-prem/local should handle the proxy. @jingzhang36 assigning this to you with thanks! |
Note: PR #1472 moves the doc to a new location (without changing the content). The new location is at https://www.kubeflow.org/docs/pipelines/installation/standalone-deployment/ |
I think there is more in that doc which is sort of mis-placed. |
This section is also very specific to
We can modify the instruction to be generic. |
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. |
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
/reopen We still want this open. |
@Bobgy: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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. |
/lifecycle frozen |
Closing this issue. It seems it's not longer needed. cc @hbelmiro feel free to re-open if you think it's still needed. |
/close |
@varodrig: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
https://www.kubeflow.org/docs/pipelines/standalone-deployment-gcp/
The text was updated successfully, but these errors were encountered: