[Core feature] Allow pod spec in Ray plugin #4674
Labels
backlogged
For internal use. Reserved for contributor team workflow.
enhancement
New feature or request
Motivation: Why do you think this is important?
The Flyte Ray plugin seems not to offer to same parameters as RayJob ATM. For us, its necessary to set the configuration for the pod (e.g. which nodepool or volume mount).
Looking at the ray documentation, there is an option to define template like this:
https://docs.ray.io/en/latest/cluster/kubernetes/user-guides/config.html
Looking at the plugin code it seems that it takes the pod template for head and worker from the pod template defined on by the "task".
Goal: What should the final outcome look like, ideally?
You should be able to specify your resources for every group (head and multiple worker groups) the same way you do for a regular flyte task.
Describe alternatives you've considered
Just forward all parameters of a ray job from python to the go plugin and ignore the pod template from task level.
Propose: Link/Inline OR Additional context
I think this has a high overlap with #4377
Are you sure this issue hasn't been raised already?
Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: