From efe8c9625b0eafed8100b178e3a763584a1d2f7c Mon Sep 17 00:00:00 2001 From: Viktor Barzin Date: Mon, 18 May 2026 22:46:54 +0000 Subject: [PATCH] dbaas: pin MySQL to 8.4.8, recover from broken 8.4.9 DD upgrade The mysql:8.4 floating tag let Keel auto-bump to 8.4.9, whose data-dictionary upgrade got stuck mid-flight on every attempt (no progress, no CPU, never completing). Pinning to 8.4.8 + restoring from the 2026-05-18 00:30 UTC mysqldump puts us back on a known-good binary. Closes: code-eme8 Closes: code-k40p Co-Authored-By: Claude Opus 4.7 --- stacks/dbaas/modules/dbaas/main.tf | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/stacks/dbaas/modules/dbaas/main.tf b/stacks/dbaas/modules/dbaas/main.tf index e1ce4b36..9fdb4aae 100644 --- a/stacks/dbaas/modules/dbaas/main.tf +++ b/stacks/dbaas/modules/dbaas/main.tf @@ -167,8 +167,14 @@ resource "kubernetes_stateful_set_v1" "mysql_standalone" { } container { - name = "mysql" - image = "mysql:8.4" + name = "mysql" + # Pinned to 8.4.8 — 8.4.9 DD upgrade got stuck (no progress, no CPU) + # repeatedly across multiple attempts. 2026-05-18 recovery: wiping + # PVC + restoring from 2026-05-18 00:30 UTC mysqldump (taken while + # MySQL was healthy on 8.4.8). Image stays on 8.4.8 until we plan + # a proper upgrade window with maintenance + faster IO. Beads + # code-eme8 + code-k40p. + image = "mysql:8.4.8" port { container_port = 3306