<#4244 [Core feature] Add support KubeRay 1.0 > Is...
# flyte-github
a
#4244 [Core feature] Add support KubeRay 1.0 Issue created by pingsutw Motivation: Why do you think this is important? Kuberay v0.3 ~v0.6 are not stable, and have many bugs and performance issues. People have run into tons of problems when using KubeRay operators. kuberay issues: • `0.3.0`: Kuberay may create two rayJob sometimes • `0.4.0`: Kuberay failed to run the RayJob when running multiple rayJobs (2+) in the same time. •
0.5.0
Kuberay add an init container but this init container doesn't have default request and limit, so it can't be run in the project-doman namespace • `0.5.1`: same issue as 0.5 • `0.5.2`: We can run the rayjob successfully but still have the problem in
0.3
• `0.6.0`: Kuberay added a k8sJob in the Rayjob, which used to submit the ray remote task, but it doesn't have default request and limit also. We should • Make sure Flyte can run a ray task when using kuberay 1.0 • Upgrade the kuberay client version in the ray plugin Goal: What should the final outcome look like, ideally? Flyte can a run ray tasks without any problems When using kuberay 1.0 Describe alternatives you've considered NA Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte