Closed ByronHsu closed 3 months ago
This is beyond the scope of KubeRay. Users should ensure they are using the correct images. Additionally, users can utilize activeDeadlineSeconds to prevent RayJobs from running indefinitely. In addition, the K8s Job status also doesn't have the information about image pull error.
Similarly, if "ray" is not found in the image, the status will be stuck at "initializing"
Discussed offline. This is beyond the scope of KubeRay. Feel free to reopen if you have further thoughts.
Search before asking
KubeRay Component
ray-operator
What happened + What you expected to happen
When users specify a bad docker image, the status is not reflected on rayjob though pods show
ImagePullBackOff
.pod status
ray job status
ray cluster status
Reproduction script
deploy the following ray job
Anything else
No response
Are you willing to submit a PR?