-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
ScaledJob: introduce rolloutStrategy
#2164
Conversation
Signed-off-by: etamarw <etamarw@wix.com>
Signed-off-by: etamarw <etamarw@wix.com>
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.
Looking good, please run make build
& make manifests
to also include regenerated CRDs and deepcopy objects.
rolloutStrategy
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.
Looking good, do you think that you can add an unit test for this feature? Similar to ScaledObject one: https://github.com/kedacore/keda/blob/main/controllers/keda/scaledobject_controller_test.go
And update documentation: https://keda.sh/docs/2.5/concepts/scaling-jobs/
@TsuyoshiUshio PTAL :) |
@etamarw any update on this please? |
sorry for the latency, had a really busy week. ill try to push relevant changes in the next few days. |
@etamarw no problem :) It would be nice to include this change into the next release which will be in (~3 weeks), so you have some time, no need to rush. Thanks! |
Signed-off-by: etamarw <etamarw@wix.com>
Signed-off-by: etamarw <etamarw@wix.com>
Co-authored-by: Aaron Schlesinger <70865+arschles@users.noreply.github.com> Signed-off-by: etamarw <etamarw@wix.com>
Co-authored-by: Aaron Schlesinger <70865+arschles@users.noreply.github.com> Signed-off-by: etamarw <etamarw@wix.com>
Signed-off-by: etamarw <etamarw@wix.com>
Signed-off-by: etamarw <etamarw@wix.com>
de39f8c
to
f10cfbc
Compare
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.
Thank you! It is very good contribution! I love your idea! I leave only one comment for @zroubalik check.
Signed-off-by: etamarw <etamarw@wix.com>
Signed-off-by: etamarw <etamarw@wix.com>
@zroubalik please make sure that i restored all of the relevant files. |
@etamarw looking good, could you please resolve the conflict in |
Signed-off-by: etamarw <etamarw@wix.com>
f73e6cc
to
3490e77
Compare
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.
this looks great @etamarw 👍
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.
@etamarw Looking good, the last thing is missing is to document this feature in here: https://github.com/kedacore/keda-docs/blob/master/content/docs/2.5/concepts/scaling-jobs.md
pr to the docs repo: kedacore/keda-docs#563 |
Co-authored-by: Zbynek Roubalik <726523+zroubalik@users.noreply.github.com> Signed-off-by: etamarw <etamarw@wix.com>
0647bff
to
57b5dc6
Compare
This pr should fix / add features as described on this issue: #2098
Checklist
Fixes #
I've added the field rolloutStrategy (gradual / immediate - the default). it lets the user to choose whether to redeploy all running jobs created by the previous version of the scalejob or to rollout new changes gradually. means only new jobs will contain the latest changes, and already running jobs wont get deleted.
also, i fixed the bug we had with returning the number of jobs the controller deletes.
its my first contribution over here so i really need a code review :)