Fix for Sample YAML Config Test - 2.4.0 Failure due to 'suspend' Field #1096
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
#926 adds the
suspend: false
field toray_v1alpha1_rayjob.yaml
. However, since this field is new and not present in the CRD of kuberay/operator:v0.5.0, it would compromise backwards compatibility.We need to ensure that sample files function with both the 0.5.0 and nightly versions, so we shouldn't add
suspend: false
now, but only after the 0.6.0 release.The failure can be reproduced:
suspend: false
will cause the Sample YAML Config Test - 2.4.0 to consistently fail :https://github.com/ray-project/kuberay/actions/runs/4995614782/jobs/8947869834
https://github.com/ray-project/kuberay/actions/runs/5008264539/jobs/8976078708
ray_v1alpha1_rayjob.yaml
is not compatible withkuberay/operator:v0.5.0
.This PR removes
suspend: false
, so that:ray_v1alpha1_rayjob.yaml
compatible withkuberay/operator:v0.5.0
.ray_v1alpha1_rayjob.yaml
compatible withnightly kuberay
. This is becasuesuspend
field is optional and if not set, it will befalse
by default.TODO
Add
suspend: false
back after 0.6.0 release.Related issue number
Checks