Go to file

Tower Bot 816328b49d tower 0.61.6 — hide platform cluster from tenant-scoped server lists

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.

2026-04-30 11:54:32 +03:00

templates

ingress: route /connect and /teardown to backend (customer-facing token endpoints)

2026-04-29 13:57:51 +03:00

backend-deployment.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail

2026-04-26 20:47:11 +03:00

Chart.yaml

Initial Tower chart

2026-04-26 18:01:44 +03:00

ingressroute.yaml

tower 0.9.0 + tower-ui 0.8.0 — capacity bars on Server Detail