From 53d8a21a19cfa06cdc2c440a2accf9beebca6b20 Mon Sep 17 00:00:00 2001 From: Tower Bot Date: Thu, 30 Apr 2026 11:47:07 +0300 Subject: [PATCH] =?UTF-8?q?tower=200.61.5=20/=20tower-ui=200.61.9=20?= =?UTF-8?q?=E2=80=94=20domain=20on=20Argo=20App,=20no=20more=20hardcode?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The instance row's '.tenants.odoosky.org' was being computed client-side from the code alone, so a tenant whose domain is '4th.online' still saw 'odoo16.tenants.odoosky.org' in the list + the Open button — wrong zone, no cert, scary Firefox warning. Backend: Argo App now carries an 'odoosky.io/domain' annotation written at create time from req.Domain (the values.yaml domain), read back in argoApplicationSummary.Domain. Delete handler reads the same annotation so DNS cleanup hits the right Cloudflare zone instead of the platform default. Frontend: Instance.domain field, used by InstancesView, Vitals, ActionBar, with a fallback to the legacy pattern for any pre-Phase-F Argo App that hasn't been backfilled yet. Backfill for live odoo16: kubectl annotate done out-of-band. --- values.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/values.yaml b/values.yaml index afa1277..c57c9b4 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.4" + tag: "0.61.5" 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.61.8" + tag: "0.61.9" pullPolicy: IfNotPresent imagePullSecrets: - name: docker-mirror-pull