-
Notifications
You must be signed in to change notification settings - Fork 445
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
[Feature] Automatically reload pods when/if the image changes in RayCluster CR #234
Comments
That's a great point. Normally a couple of questions are raised with the image upgrade: 1- is the assumption that the new image compatible with the old image? 2- should all pods be updated in a single step, or do we perform a rolling upgrade? |
@jeffreyftang @akanso PR #231 address this issue. If you guys have time, please have another review. This was to address #155 |
I tried changing
|
Search before asking
Description
Currently, changing things like the number of worker replicas in the ray cluster CR will be detected and actioned by the operator. However, changing the image used isn't.
My understanding is that this behavior is implemented here:
kuberay/ray-operator/controllers/raycluster_controller.go
Line 196 in d54ea70
Use case
Essentially, after upgrading or modifying a ray cluster CR with a new image, I'd like that image to be automatically picked up by any existing pods.
Related issues
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: