Context
The auto-upgrade CronJob (introduced in #69) currently runs once daily at 02:23 UTC. Customers freeze on whatever version they had at install time until the next 02:23 tick — up to ~24h of drift after a chart release.
Change
Switch the default schedule in client/values.yaml from "23 2 * * *" to "23 * * * *" so deployed clients converge on the latest chart within ~1h instead of ~24h.
Rollout
Two PRs, same single-line change:
- One into
develop so the dev integration branch keeps in sync.
- One cherry-picked onto a branch off
main so prod gets only this change without pulling every other unshipped dev commit along with it.
Acceptance criteria
client/values.yaml autoUpgrade.schedule is "23 * * * *" on both develop and main.
- Existing
auto_upgrade_test.yaml continues to pass.
- Comment above the schedule key reflects the new cadence.
Context
The auto-upgrade CronJob (introduced in #69) currently runs once daily at 02:23 UTC. Customers freeze on whatever version they had at install time until the next 02:23 tick — up to ~24h of drift after a chart release.
Change
Switch the default schedule in
client/values.yamlfrom"23 2 * * *"to"23 * * * *"so deployed clients converge on the latest chart within ~1h instead of ~24h.Rollout
Two PRs, same single-line change:
developso the dev integration branch keeps in sync.mainso prod gets only this change without pulling every other unshipped dev commit along with it.Acceptance criteria
client/values.yamlautoUpgrade.scheduleis"23 * * * *"on bothdevelopandmain.auto_upgrade_test.yamlcontinues to pass.