-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[post-0.4.0 KubeRay release] Update KubeRay versions #821
[post-0.4.0 KubeRay release] Update KubeRay versions #821
Conversation
Signed-off-by: Dmitri Gekhtman <[email protected]>
@Jeffwan @scarlet25151 I did not modify KubeRay versions in files related to the CLI or API server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall LGTM.
@sihanwang41 can make the call on when to merge this. |
version: 0.3.0 | ||
|
||
# This is the version number of the application being deployed. This version number should be | ||
# incremented each time you make changes to the application. Versions are not expected to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to use helm version to track the upgrade in future?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you elaborate?
The version
field is still there.
I add ci bot back and let's check how the CI works |
@scarlet25151 Please update the apiserver versions in a follow up PR. |
Signed-off-by: Dmitri Gekhtman <[email protected]> Signed-off-by: Dmitri Gekhtman <[email protected]>
Signed-off-by: Dmitri Gekhtman [email protected]
Why are these changes needed?
Updates KubeRay versions in master.
To be merged after images and Helm charts are built.
Related issue number
Checks