From b89c084ebd024236b8d5f23ad75411113e37d611 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 29 Apr 2026 20:58:26 +0300 Subject: [PATCH] =?UTF-8?q?tower=200.60.0=20/=20tower-ui=200.61.0=20?= =?UTF-8?q?=E2=80=94=20Phase=20F.1:=20three=20buckets=20per=20tenant?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Data model: PlatformTenant.S3 = { Endpoint, Region, Buckets: { Backups, Templates, Audit } } Vault: legacy v3/data/s3{,-templates,-audit} paths wiped (decision in docs/decisions/0001 path is bring-your-own only; per-tenant only). UI: 3 bucket fields (Backups / Templates / Audit), single endpoint + region + credential pair. Test does HeadBucket on each configured bucket and reports per-bucket pass/fail. Note: writers (audit/templates/backups handlers) still read from old paths. Phase F.2 (next) sweeps the ~30 call sites onto a tenant-scoped s3Factory. Tower compiles + serves API; backups+audit+templates writes are non-functional until F.2 lands. v3 has no customers, so the breakage window is tolerable per memory feedback_v3_disposable_no_customers. --- values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/values.yaml b/values.yaml index d808c6b..9ce0f8c 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.59.2" + tag: "0.60.0" pullPolicy: IfNotPresent imagePullSecrets: - name: docker-mirror-pull @@ -29,7 +29,7 @@ frontend: enabled: true image: repository: registry.odoosky.cloud/odoosky/docker-mirror/tower-ui - tag: "0.60.0" + tag: "0.61.0" pullPolicy: IfNotPresent imagePullSecrets: - name: docker-mirror-pull