[X] I searched the issues and found no similar issues.
KubeRay Component
apiserver
What happened + What you expected to happen
The version attribute for a Ray Job is currently not used. There is no way of specifying the Ray Cluster version when launching a Ray Job. While I'm not sure how this version number is used in the controller (didn't find anything after a quick search), it is preventing me from using job metadata:
if !constraint.Check(v) { return "", fmt.Errorf("the Ray version must be at least 2.6.0 to use the metadata field") }
We support version in the Cluster protobuf, but we don't have it in the ClusterSpec protobuf, which is used by the Job protobuf.
Reproduction script
Create a Ray Job with metadata will cause the deployment to fail:
Search before asking
KubeRay Component
apiserver
What happened + What you expected to happen
The version attribute for a Ray Job is currently not used. There is no way of specifying the Ray Cluster version when launching a Ray Job. While I'm not sure how this version number is used in the controller (didn't find anything after a quick search), it is preventing me from using job metadata:
if !constraint.Check(v) { return "", fmt.Errorf("the Ray version must be at least 2.6.0 to use the metadata field") }
We support version in the Cluster protobuf, but we don't have it in the ClusterSpec protobuf, which is used by the Job protobuf.Reproduction script
Create a Ray Job with metadata will cause the deployment to fail: