From 816328b49dcd0fc636eb50fa6717dc92d69bf3f8 Mon Sep 17 00:00:00 2001 From: Tower Bot Date: Thu, 30 Apr 2026 11:54:32 +0300 Subject: [PATCH] =?UTF-8?q?tower=200.61.6=20=E2=80=94=20hide=20platform=20?= =?UTF-8?q?cluster=20from=20tenant-scoped=20server=20lists?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit handleListServers's existing tenant filter would still admit a platform cluster (type='platform') if it had been mis-labeled with a tenant or if a tenant happened to host an instance there. Belt- and-braces: explicit reject of any cluster with type='platform' when the request is tenant-scoped (non-super-admin). The platform control-plane runs Tower itself + platform-tenant template builds — it is not a deployment target for customer tenants and surfacing it in their Server picker breaks the bring-your-own-cluster model. Caught while smoke-testing MigrateDrawer: a fresh tenant's Server dropdown defaulted to 'Platform server', risking a customer deploying their tenant data onto the operator's shared infra by accident. --- values.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/values.yaml b/values.yaml index c57c9b4..316922e 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.5" + tag: "0.61.6" pullPolicy: IfNotPresent imagePullSecrets: - name: docker-mirror-pull