From 742adfff92768eddeb26a19f5a6efdc673efb400 Mon Sep 17 00:00:00 2001
From: Claude <claude@havari.me>
Date: Wed, 29 Apr 2026 20:36:46 +0300
Subject: [PATCH] =?UTF-8?q?tower=200.59.2=20=E2=80=94=20bring-your-own=20o?=
 =?UTF-8?q?nly:=20drop=20platform-Vault=20rung=20from=20CF=20resolver?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Per docs/decisions/0001-platform-fallback-deferred.md, instance DNS
automation no longer silently falls back to v3/platform/cloudflare-token.
Tenants without a configured CF token get a clear error at instance
create instead of pretending to work via shared infrastructure.
The platform Vault entry stays seeded for future revival.
---
 values.yaml | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/values.yaml b/values.yaml
index 34791dd..4b3aedc 100644
--- a/values.yaml
+++ b/values.yaml
@@ -8,8 +8,7 @@ backend:
     # the docker-mirror-pull deploy token (read-only registry scope),
     # 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.59.1"
+    tag: "0.59.2"
     pullPolicy: IfNotPresent
   imagePullSecrets:
     - name: docker-mirror-pull