-
Notifications
You must be signed in to change notification settings - Fork 29
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
REP: KubeRay RayService Incremental Rollout #58
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: ryanaoleary <ryanaoleary@google.com>
metadata: | ||
name: example-rayservice | ||
spec: | ||
upgradeStrategy: "NewCluster" |
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.
It's not too late to change this API since it's not released yet, should we change this now before v1.3 so it'll play nicely with the new fields you're proposing here?
spec:
upgradeStrategy:
type: "NewCluster"
targetCapacity: 50
maxSurgePercent: 50
...
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.
At least for 1.3, we can just support
spec:
upgradeStrategy:
type: NewCluster
So it's easy to add new fields in v1.4 that are compatible with the upgradeStrategy
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.
Oh yeah I like that idea, I'll edit the REP to reflect that and put out a PR with the API fix.
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.
a5ea9db, API change: ray-project/kuberay#2678
Signed-off-by: ryanaoleary <ryanaoleary@google.com>
Add REP for RayService incremental upgrade strategy using
max_surge_percent
and Gateway API.