You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Flyte creates Ray Jobs using v1alpha1 instead of v1. Have an option to use v1 instead of v1alpha1 before v1alpha1 deprecation in KubeRay 1.2.0.
Similar to this issue, but this now leverages the v1 CRD as an option.
Expected behavior
Enable users of Flyte to use the later CRD version of Ray jobs provided by KubeRay. These CRDs have more configurations for Ray workloads.
Additional context to reproduce
No response
Screenshots
No response
Are you sure this issue hasn't been raised already?
Yes
Have you read the Code of Conduct?
Yes
The text was updated successfully, but these errors were encountered:
It's great to see your interest in enabling the use of the later CRD version for Ray jobs in Flyte. Your contribution to provide an option for using v1 instead of v1alpha1 would be valuable for the community. Thank you for considering this enhancement!
This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.
Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.
If you want to continue the conversation, start your reply with @dosu-bot.
Describe the bug
Currently Flyte creates Ray Jobs using v1alpha1 instead of v1. Have an option to use v1 instead of v1alpha1 before v1alpha1 deprecation in KubeRay 1.2.0.
Similar to this issue, but this now leverages the v1 CRD as an option.
Expected behavior
Enable users of Flyte to use the later CRD version of Ray jobs provided by KubeRay. These CRDs have more configurations for Ray workloads.
Additional context to reproduce
No response
Screenshots
No response
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: