[Documentation] Migration guides from `<other product>` to Ray.

[dynamicwebpaige]

Search before asking

• [X] I had searched in the issues and found no similar feature requirement.

Description

Motivation

Several users have indicated interest in migrating from tools like Kubeflow, Katib, Papermill, Papermill MLFlow, Vizier, etc. to Ray and its component libraries. Given the lack of documentation for these migrations, most users are discovering and re-discovering best practices on their own.

Requested Documentation

ray.io should host tutorials to support the most common migration scenarios (list still in progress):

• Katib to Tune
• Kubeflow to Ray
• Vizier to Tune
• Papermill to Ray Core, Ray Serve, Ray Workflows
• Papermill MLFlow to Ray Core, Ray Serve, Ray Workflows, MLFlow

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• [ ] Yes I am willing to submit a PR!

[stale[bot]]

Hi, I'm a bot from the Ray team :)

To help human contributors to focus on more relevant issues, I will automatically add the stale label to issues that have had no activity for more than 4 months.

If there is no further activity in the 14 days, the issue will be closed!

• If you'd like to keep the issue open, just leave any comment, and the stale label will be removed!
• If you'd like to get more attention to the issue, please tag one of Ray's contributors.

You can always ask for help on our discussion forum or Ray's public slack channel.

[stale[bot]]

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!