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

[BUG] Have option to use v1 instead of v1alpha1 for Ray Jobs #4802

Closed
2 tasks done
peterghaddad opened this issue Jan 31, 2024 · 1 comment · Fixed by #4818
Closed
2 tasks done

[BUG] Have option to use v1 instead of v1alpha1 for Ray Jobs #4802

peterghaddad opened this issue Jan 31, 2024 · 1 comment · Fixed by #4818
Assignees
Labels
bug Something isn't working enhancement New feature or request

Comments

@peterghaddad
Copy link
Contributor

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?

  • Yes

Have you read the Code of Conduct?

  • Yes
@peterghaddad peterghaddad added bug Something isn't working untriaged This issues has not yet been looked at by the Maintainers labels Jan 31, 2024
Copy link

dosubot bot commented Jan 31, 2024

🤖

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.

@dosubot dosubot bot added the enhancement New feature or request label Jan 31, 2024
@eapolinario eapolinario removed the untriaged This issues has not yet been looked at by the Maintainers label Feb 1, 2024
@eapolinario eapolinario self-assigned this Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants