From 48a5e6eac0be8304a607d5228743f36c4a486ef3 Mon Sep 17 00:00:00 2001 From: tegwick Date: Tue, 11 Aug 2026 23:18:14 +0200 Subject: [PATCH] Point core-hub production values at forgejo.coulomb.social helm/core-hub-values.yaml was the last file still pulling from gitea.coulomb.social. Both hostnames resolve, but to different machines - gitea.coulomb.social to 92.205.130.254 (CoulombCore) and forgejo.coulomb.social to 92.205.62.239 (Railiance01) - so this quietly deployed core-hub from the frozen CoulombCore registry rather than failing loudly. Every other values file in this repo, including charts/core-hub/values.yaml for the same app, already used forgejo. The tag is a render-time placeholder; deploys pass CORE_HUB_IMAGE_TAG=, so the next core-hub rollout must confirm that sha is present on the Forgejo registry before promoting. Co-Authored-By: Claude Opus 5 --- helm/core-hub-values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/helm/core-hub-values.yaml b/helm/core-hub-values.yaml index 2c77c20..e89aa30 100644 --- a/helm/core-hub-values.yaml +++ b/helm/core-hub-values.yaml @@ -3,7 +3,7 @@ # the Secret 'core-hub-prod-env' in the core-hub namespace. image: - repository: gitea.coulomb.social/coulomb/core-hub + repository: forgejo.coulomb.social/coulomb/core-hub tag: "production-placeholder" # Render baseline only; deploy requires CORE_HUB_IMAGE_TAG=. runtime: