Skip to content
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

Closed
sarahmaddox opened this issue Oct 17, 2019 · 15 comments
Assignees
Labels

Comments

@sarahmaddox
Copy link
Contributor

https://www.kubeflow.org/docs/pipelines/standalone-deployment-gcp/

@issue-label-bot issue-label-bot bot added the kind/feature KIND: Features label Oct 17, 2019
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.86. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@sarahmaddox
Copy link
Contributor Author

/assign

@sarahmaddox sarahmaddox changed the title Move Pipelines standalone deployment to the GCP section of the docs Update Pipelines standalone deployment to describe generic standalone (as well as GCP) Dec 10, 2019
@sarahmaddox
Copy link
Contributor Author

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!

@jbottum jbottum added area/pipelines AREA: Kubeflow Pipelines priority/p2 labels Dec 15, 2019
@sarahmaddox
Copy link
Contributor Author

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/

@goswamig
Copy link
Contributor

I think there is more in that doc which is sort of mis-placed.
For e.g. section Before you get started has sub section setup your cluster. I think in that sub section we can add reference to creation of cluster from AWS, Azure and GCP pages or just assume that user has cluster.

@goswamig
Copy link
Contributor

This section is also very specific to gcp.

Get the public URL for the Kubeflow Pipelines UI and use it to access the Kubeflow Pipelines UI:

We can modify the instruction to be generic.

@stale
Copy link

stale bot commented Jun 29, 2020

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
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
platform/aws 0.67
area/docs 0.97

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@Bobgy
Copy link
Contributor

Bobgy commented Aug 7, 2020

/reopen

We still want this open.
Also FYI, we have already provided a platform agnostic env: https://github.com/kubeflow/pipelines/tree/master/manifests/kustomize/env/platform-agnostic. It should be good for general installation.

@k8s-ci-robot
Copy link
Contributor

@Bobgy: Reopened this issue.

In response to this:

/reopen

We still want this open.
Also FYI, we have already provided a platform agnostic env: https://github.com/kubeflow/pipelines/tree/master/manifests/kustomize/env/platform-agnostic. It should be good for general installation.

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.

@k8s-ci-robot k8s-ci-robot reopened this Aug 7, 2020
@stale stale bot removed the lifecycle/stale label Aug 7, 2020
@stale
Copy link

stale bot commented Nov 6, 2020

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.

@stale stale bot added the lifecycle/stale label Nov 6, 2020
@Bobgy
Copy link
Contributor

Bobgy commented Nov 6, 2020

/lifecycle frozen

@varodrig
Copy link
Contributor

varodrig commented Jan 10, 2025

Closing this issue. It seems it's not longer needed. cc @hbelmiro feel free to re-open if you think it's still needed.

@varodrig
Copy link
Contributor

/close

Copy link

@varodrig: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants