#3763 [Docs] Only kuberay 0.3.0 is supported Issue created by eapolinario Description We've seen reports of different bugs in the latest few kuberay reports, more specifically: • 0.4: they changed reconcile logic in the operator. if you run the ray job, the status will always be pending. kuberay community didn’t test it, and release it. • 0.5: they inject init container into worker nodes, and didn’t set the resource (cpu, memory) for the init container. therefore, we can’t run the rayjob because there is k8s quota in every project-domain namespace, and quota requires every container to set the cpu, mem. We should make it apparent that the current ray extension only works with the version 0.3.0 of the kuberay operator. Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte