Discussion: In Spotify’s setup, Ray and Flyte are run on different clusters. KubeRay also has an API server, and they want to use Propeller to send a http request to Ray api server to create ray job. Therefore, we may need to add a ray webAPI plugin in propeller. Start a new thread to discuss this. Is there any other better way to handle this? cc @thankful-minister-83577 @freezing-airport-6809 @rapid-autumn-97122

yeah @rapid-autumn-97122 i know you brought this up in the past, but is there any chance you can add flyte to the ray cluster?

hmm, does that mean we need to install Propeller on our ray cluster? do you mind elaborating more on this? thank you!

yeah… though it’s not possible to scan the workflow right now is it @acceptable-policeman-57188 do you know?

are you asking how do we assign specific executions to specific flytepropeller clusters?

yeah

we don't have anything that's workflow-aware, right now it's just a static mapping: https://docs.flyte.org/en/latest/deployment/multicluster.html#user-and-control-plane-deployment

thanks katrina. so yeah never mind @rapid-autumn-97122 for the current plugin to be useful, the kuberay operator will need to be installed on the flyte cluster. is this not possible?

yeah it’s not working with our current setup since Ray and Flyte are owned by different teams and operated on different GKE clusters.

and there’s no way to add the ray operator to the flyte cluster?

Can’t we load the creeds for the ray cluster and submit the job resource there?

@swift-animal-75798 we can, but this causes a lot or problems, you folks did it for FlinkOperator if you remember and should work with Ray

yeah i am asking because we already work in this way with a flink task and the FlinkOperator which is running on a different GKE cluster (more resources available for massive jobs)