Skip to content
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][RayService]Add kubernetes event to inform user of upgrade strategy #2592

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

chiayi
Copy link
Contributor

@chiayi chiayi commented Dec 2, 2024

Why are these changes needed?

Adds Kubernetes Event to inform users of upgrade strategy. Ex:

Screenshot 2024-12-02 at 1 21 01 PM

Related issue number

Part of #2554

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

@chiayi chiayi force-pushed the rayservice-upgrade branch 3 times, most recently from 9ea70da to b9b7186 Compare December 3, 2024 21:43
}
r.Recorder.Event(rayServiceInstance, "Normal", "UpgradeStrategy", strategyMessage)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we previsouly discussed this event only being emitted when the upgrade is triggered. Is this the case if we only emit the event when the cluster action is RolloutNew?

Copy link
Contributor Author

@chiayi chiayi Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changed to only emit event if zero downtime triggers an upgrade.

I've also went back to do another manual test to check the behavior of zero downtime (before changing the event to only emit on upgrade). When there is an upgrade with the "RolloutNew" but with zero downtime disabled, it will continue to retry:
Screenshot 2024-12-03 at 5 10 28 PM

@chiayi chiayi force-pushed the rayservice-upgrade branch 2 times, most recently from c3d89bb to 5dfc132 Compare December 4, 2024 20:26
@andrewsykim andrewsykim self-assigned this Dec 11, 2024
@chiayi chiayi force-pushed the rayservice-upgrade branch from 5dfc132 to 31f171a Compare December 12, 2024 19:18
@chiayi
Copy link
Contributor Author

chiayi commented Dec 12, 2024

Screenshot 2024-12-12 at 11 17 04 AM

@chiayi chiayi marked this pull request as ready for review December 12, 2024 19:18
@chiayi chiayi requested a review from andrewsykim December 13, 2024 21:24
Copy link
Collaborator

@andrewsykim andrewsykim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small nit

ray-operator/controllers/ray/rayservice_controller.go Outdated Show resolved Hide resolved
@chiayi chiayi force-pushed the rayservice-upgrade branch from 31f171a to 68f0388 Compare December 18, 2024 01:15
@chiayi chiayi force-pushed the rayservice-upgrade branch 2 times, most recently from 53da055 to b385ebf Compare December 18, 2024 02:09
@chiayi chiayi force-pushed the rayservice-upgrade branch from b385ebf to d78a439 Compare December 18, 2024 02:25
@andrewsykim andrewsykim merged commit c8f826b into ray-project:master Dec 18, 2024
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants