-
Notifications
You must be signed in to change notification settings - Fork 11
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
feat!: enable horizontal autoscaling of Liquid Legions v2 Mill via CronJobs #1686
Conversation
6ebc86a
to
69fb087
Compare
69fb087
to
b42c43e
Compare
b42c43e
to
dd6b9e5
Compare
dd6b9e5
to
e7d0444
Compare
beaaf89
to
9e4b0a7
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.
Can you add a document that describes how to roll this out?
Are we keeping the daemon images/configs until the cron has been successfully rolled out by our clients?
Reviewable status: 0 of 72 files reviewed, all discussions resolved
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.
Note that this PR is still a draft while I work on testing out the interaction between the cluster autoscaler and CronJobs.
Can you add a document that describes how to roll this out?
It'll be part of the release notes. It's not really different than any other change to our K8s object configs.
Are we keeping the daemon images/configs until the cron has been successfully rolled out by our clients?
No. As mentioned above, it's similar to other changes we push out regularly.
Reviewable status: 0 of 72 files reviewed, all discussions resolved
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.
To clarify the above statement regarding keeping the daemon images: the new release will have the image be for a job rather than a daemon. Previous releases will still be a daemon.
Reviewable status: 0 of 72 files reviewed, all discussions resolved
7867995
to
f58dbfa
Compare
f58dbfa
to
bed5aa4
Compare
bed5aa4
to
383a07e
Compare
ccb8f26
to
a5db8ec
Compare
Depends on #1692 |
a5db8ec
to
a9da686
Compare
9d36901
to
8760f1c
Compare
a9da686
to
91d6ba9
Compare
The name is too long for the standard metadata name field. BREAKING CHANGE: Renames a K8s Deployment in the dev configuration.
91d6ba9
to
d4ae8c5
Compare
d4ae8c5
to
d79da06
Compare
Dropping this in favor of #1697 |
This converts the Liquid Legions v2 Mill from a K8s Deployment to a CronJob.
BREAKING CHANGE: The Liquid Legions v2 Mill container images are now single jobs rather than daemons, where the
--polling-interval
option is replaced by a--grace-period
option.BREAKING CHANGE: The Liquid Legions v2 Mill daemon Deployment has been replaced by a CronJob.
BREAKING CHANGE: A CronJob scheduler Deployment must exist in each Duchy cluster with appropriate access to the K8s API in the cluster.