From 042d1ce1ac0a69d4db334dcfc285ffd6b2a9341e Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Wed, 17 Jun 2026 13:28:58 +0000 Subject: [PATCH] k8s-version-upgrade: CI-retrigger to apply D1 (missed by two-commit diff-base) fb638cd8 landed as two commits; the apply pipeline diffed against HEAD~1 (the monitoring-only commit) and never applied stacks/k8s-version-upgrade, so the retry-on-failure logic isn't live yet. This single-commit retrigger forces it. Co-Authored-By: Claude Opus 4.8 --- stacks/k8s-version-upgrade/main.tf | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/stacks/k8s-version-upgrade/main.tf b/stacks/k8s-version-upgrade/main.tf index 58e5715c..e036ef91 100644 --- a/stacks/k8s-version-upgrade/main.tf +++ b/stacks/k8s-version-upgrade/main.tf @@ -534,3 +534,8 @@ resource "kubernetes_cron_job_v1" "k8s_version_check" { # CI retrigger v5 2026-05-16T23:10:38Z # CI retrigger v6 2026-05-16T23:18:58Z + +# CI retrigger 2026-06-17 — apply D1 retry-on-failure. The two-commit landing +# of fb638cd8 left the changed-stack detection diffing against HEAD~1 (commit 2, +# monitoring-only), so this stack's changes (commit 1) were never applied; a +# fresh single commit guarantees the diff includes stacks/k8s-version-upgrade.