Go to file

Tower Bot 53d8a21a19 tower 0.61.5 / tower-ui 0.61.9 — domain on Argo App, no more hardcode

The instance row's '<code>.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.

2026-04-30 11:47:07 +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