[RayService] A new RayCluster should not be prepared if the serve service points to the existing pending cluster

[kevin85421]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

The RayService controller updates the head and serve services to point to the pending cluster when it is ready, then promotes the pending cluster to the active cluster. However, it seems possible that the services have already pointed to the pending RayCluster, but RayService decides to prepare a new cluster because the user updated the RayService spec.

Then, the old pending cluster will be removed, and requests may be dropped.

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[kevin85421]

/assign @rueian