k8s-version-upgrade: move detection to nightly 23:00 UTC (overnight upgrades)
Some checks failed
ci/woodpecker/push/default Pipeline failed
Some checks failed
ci/woodpecker/push/default Pipeline failed
Disruptive node drains should run when the cluster is idle. Move the
k8s-version-check detection CronJob from 12:00 UTC (noon) to 23:00 UTC
(00:00 London) — overnight, low usage, and clear of the kured OS-reboot window
(01:00-05:00 UTC) so the two drain pipelines never overlap. (Viktor, 2026-06-17.)
- stacks/k8s-version-upgrade/main.tf: var.schedule default 0 12 → 0 23 * * *.
- scripts/upgrade_state.sh: next_scheduled_run_utc now computes the 23:00 slot
(was next_daily_noon_utc).
- docs (runbook, architecture) + upgrade-state SKILL: schedule references
updated to 23:00 UTC nightly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
ed53b34bf4
commit
c04efa3d3a
5 changed files with 22 additions and 21 deletions
|
|
@ -27,12 +27,13 @@
|
|||
|
||||
variable "schedule" {
|
||||
type = string
|
||||
# Daily 12:00 UTC — outside kured window (kured runs 02:00-06:00
|
||||
# London). Was weekly Sunday until 2026-05-18; daily picks up upstream
|
||||
# patch releases the same day they land. Concurrency is bounded by the
|
||||
# CronJob's Forbid policy + Job-name idempotency (the detection job
|
||||
# skips spawning a preflight Job if one already exists).
|
||||
default = "0 12 * * *"
|
||||
# Nightly 23:00 UTC (00:00 London) — overnight / low cluster usage, and clear
|
||||
# of the kured OS-reboot window (01:00-05:00 UTC = 02:00-06:00 London) so the
|
||||
# two drain-pipelines never overlap. Moved from 12:00 UTC noon on 2026-06-17
|
||||
# (Viktor: disruptive node drains should run overnight). Was weekly Sunday
|
||||
# until 2026-05-18. Concurrency bounded by the CronJob's Forbid policy +
|
||||
# retry-on-failure Job-name idempotency.
|
||||
default = "0 23 * * *"
|
||||
}
|
||||
|
||||
variable "enabled" {
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue