From 61669ff7045ed3d84ce39252f6862ef943dcb7fb Mon Sep 17 00:00:00 2001
From: Tower Bot <tower@odoosky.org>
Date: Thu, 30 Apr 2026 11:12:28 +0300
Subject: [PATCH] =?UTF-8?q?tower=200.61.3=20=E2=80=94=20fix=20CF=20token?=
 =?UTF-8?q?=20Vault=20key=20mismatch?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

cloudflare_resolver.go reads data['token'] but the writer (and the
test endpoint) stores under data['api_token']. Result: every fresh
tenant's CF resolver returned no token even when one was saved,
killing DNS records view AND any instance lifecycle DNS write.

Caught while smoke-testing the multi-tenant signup flow.
---
 values.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/values.yaml b/values.yaml
index 419c4be..4e4316c 100644
--- a/values.yaml
+++ b/values.yaml
@@ -9,7 +9,7 @@ backend:
     # so every cluster that runs Tower needs the same imagePullSecret
     # provisioned out-of-band (until cluster-platform-v3 owns it).
     repository: registry.odoosky.cloud/odoosky/docker-mirror/tower
-    tag: "0.61.2"
+    tag: "0.61.3"
     pullPolicy: IfNotPresent
   imagePullSecrets:
     - name: docker-mirror-pull