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

Document Removal of Kubeflow Pipelines from AAW #1470

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

StanHatko
Copy link
Contributor

Document removal of this feature, and goal (as I understand it) to replace with Argo Workflows.

@StanHatko
Copy link
Contributor Author

@wg102 Is this correct, or are there errors (for instance is Argo Workflows the plan, last I heard it was but that was a while ago)?

@StanHatko StanHatko mentioned this pull request Dec 9, 2022
5 tasks
@wg102
Copy link
Contributor

wg102 commented Dec 23, 2022

We are currently testing thoroughly the removal of pipelines in dev. Once that is done, and approved, the docs will be removed as well
But that is the plan, yes @StanHatko

@StanHatko
Copy link
Contributor Author

We should at least put a warning box on the AAW Kubeflow pipelines page in the meantime, saying that the feature will be removed. This will remove the possibility of a user who sees that page investing time and effort into testing and using Kubeflow pipelines on AAW only to find it not working or removed.

@StanHatko
Copy link
Contributor Author

@wg102 Created the new pull request #1516 to add warning box to the Kubeflow pipelines page in the AAW documentation, noting the upcoming removal of the feature.

Collinbrown95
Collinbrown95 previously approved these changes Feb 1, 2023
Copy link
Contributor

@Collinbrown95 Collinbrown95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Collinbrown95
Copy link
Contributor

@StanHatko Can you please resolve the merge conflict? Other than that, this PR should be ready to merge!

@StanHatko
Copy link
Contributor Author

I've resolved the merge conflict.

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

Successfully merging this pull request may close these issues.

4 participants