[X] I searched the issues and found no similar issues.
KubeRay Component
ray-operator, Others
What happened + What you expected to happen
I added a priority class name to both my head spec and worker spec. When I inspect the final templated yaml coming from the Kuberay CRD I see that the priority class name is included for the head group but not the worker group. This has the effect of transparently dropping the priority class name in the worker group spec. Upon manually editing the RayCluster CRD on kubernetes to insert the priority class name, it is forwarded to the pod definitions.
Reproduction script
Just include a priority class name in RayCluster object in yaml for head spec and worker spec.kubectl describe RayCluster my-cluster will then show you the priority class name is shown in the head spec but dropped for worker spec.
Search before asking
KubeRay Component
ray-operator, Others
What happened + What you expected to happen
I added a priority class name to both my head spec and worker spec. When I inspect the final templated yaml coming from the Kuberay CRD I see that the priority class name is included for the head group but not the worker group. This has the effect of transparently dropping the priority class name in the worker group spec. Upon manually editing the RayCluster CRD on kubernetes to insert the priority class name, it is forwarded to the pod definitions.
Reproduction script
Just include a priority class name in RayCluster object in yaml for head spec and worker spec.
kubectl describe RayCluster my-clusterwill then show you the priority class name is shown in the head spec but dropped for worker spec.Anything else
No response
Are you willing to submit a PR?