From 6a335132fe4dd841e32a9245b3e384d4dc410172 Mon Sep 17 00:00:00 2001 From: Scooby Husky Date: Thu, 20 Aug 2026 21:18:13 -0500 Subject: [PATCH] VPS GitLab: disable upgradeCheck hook (breaks fresh installs via ArgoCD) Co-Authored-By: Claude Sonnet 5 --- infrastructure/vps-standby/gitlab/values.yaml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/infrastructure/vps-standby/gitlab/values.yaml b/infrastructure/vps-standby/gitlab/values.yaml index 58cd94d..ed8ad0f 100644 --- a/infrastructure/vps-standby/gitlab/values.yaml +++ b/infrastructure/vps-standby/gitlab/values.yaml @@ -69,6 +69,19 @@ global: - secret: gitlab-oidc-secret key: provider +# GitLab's pre-upgrade hook checks the deployed version against a +# previous-release ConfigMap to enforce supported upgrade paths - found +# live 2026-08-21 that it fails with "unsupported upgrade path" on a +# genuinely FRESH install too (confirmed: no prior chart-info ConfigMap, +# no Helm release secret, brand new namespace) - a chart/ArgoCD +# interaction quirk (ArgoCD doesn't do real `helm install`, so the +# optional chart-info ConfigMap's absence apparently isn't handled the +# way the script expects). Not relevant for a fresh install anyway - only +# matters for real version-to-version upgrades, which is a future concern +# once this is actually running something to upgrade FROM. +upgradeCheck: + enabled: false + postgresql: install: false