Skip to main content
11.0.0 runs exclusively on Metoro’s new-generation telemetry tables. A fresh 11.x installation creates only the new tables and serves every query from them. A 10.x hub stores its telemetry in the previous-generation tables, which the new release neither writes nor reads.
Do not helm upgrade an existing 10.x hub to 11.0.0. The upgrade would stop writing the tables your existing telemetry lives in and make that data invisible to queries. The chart refuses to render against the 11.0.0 defaults unless newTelemetryTablesAcknowledged: true is set in your values, which you should only do for a fresh installation.

What to do instead

  • New installations: install 11.0.0 directly by following the installation guide. The installation planner generates values with the acknowledgement already set.
  • Existing 10.x hubs: stay on the 10.x release line and contact Metoro support. Migration tooling that backfills existing telemetry into the new-generation tables is arriving shortly; Metoro support will confirm the migration plan for your installation and the 10.x-to-11.x upgrade path once it applies to you.
The chart values API is unchanged from 10.x: your existing values files remain valid with no configuration changes, and they will carry over as-is when the migration path applies to your installation. The only 11.x addition is the newTelemetryTablesAcknowledged: true confirmation.

Why this is a hard break

The new-generation tables change the physical storage layout: attributes move from map columns to typed JSON columns, and tables are partitioned by retention cohort. Queries against one generation cannot read the other’s data, so a hub must either keep serving from the old tables (10.x) or have its history migrated before serving from the new ones (11.x). Metoro chose an explicit migration step over a silent in-place flip so that no installation loses sight of its existing telemetry.