You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[cherry-pick] Generate RayCluster Hash on KubeRay Version Change (#2320) (#2339)
* Re-generate hash when KubeRay version changes
* Change logic to DoNothing on KubeRay version mismatch
* Add KubeRay version annotation to test
* Move update logic
* Update rayservice_controller.go
* Add unit test
* Add period
* Go vet changes
* Update rayservice_controller_unit_test.go
* Address test comments
---------
Signed-off-by: Ryan O'Leary <[email protected]>
Signed-off-by: ryanaoleary <[email protected]>
Co-authored-by: ryanaoleary <[email protected]>
// Test 1: Neither active nor pending clusters exist. The `markRestart` function will be called, so the `PendingServiceStatus.RayClusterName` should be set.
748
751
"Zero-downtime upgrade is enabled. Neither active nor pending clusters exist.": {
// Test 6: If the active KubeRay version doesn't match the KubeRay version annotation on the RayCluster, update the RayCluster's hash and KubeRay version
786
+
// annotations first before checking whether to trigger a zero downtime upgrade. This behavior occurs because when we upgrade the KubeRay CRD, the hash
787
+
// generated by different KubeRay versions may differ, which can accidentally trigger a zero downtime upgrade.
788
+
"Active RayCluster exists. KubeRay version is mismatched. Update the RayCluster.": {
0 commit comments