viktor/infra
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

k8s-version-upgrade: CI-retrigger to apply D1 (missed by two-commit diff-base)
All checks were successful
ci/woodpecker/push/default Pipeline was successful
Details

Browse source 
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 <noreply@anthropic.com>
This commit is contained in:
Viktor Barzin 2026-06-17 13:28:58 +00:00
parent fb638cd8ec
commit 042d1ce1ac
1 changed files with 5 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
stacks/k8s-version-upgrade/main.tf
View file

@ -534,3 +534,8 @@ resource "kubernetes_cron_job_v1" "k8s_version_check" {
# CI retrigger v5 2026-05-16T23:10:38Z # CI retrigger v5 2026-05-16T23:10:38Z
# CI retrigger v6 2026-05-16T23:18:58Z # 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.