Skip to main content
Metoro 10.4.0 is a minor release in the 10.x on-premises line. It keeps the 10.x Helm values API, so existing 10.3.0 values files can be reused without migration. No ClickHouse reset, PostgreSQL migration, Temporal migration, or datastore maintenance step is required for this upgrade.
When ai.enabled=true, Metoro 10.4.0 also pulls the Guardian runner, Agent Sandbox controller, and sandbox router images. If you mirror or allowlist images individually, add or update the following values before upgrading:
  • images.guardianRunner
  • images.agentSandboxController
  • images.agentSandboxRouter
global.imageRepositoryOverride rewrites the default Metoro repositories automatically, but the corresponding image paths and tags must exist in that registry. If you override images.agentSandboxController individually, keep the agentSandbox.image dependency pass-through value in sync; the chart validates these values during rendering.
Hub commands assume the Helm release is named metoro and runs in the metoro-hub namespace. Monitored-cluster exporter commands assume the Helm release is named metoro-exporter and runs in the metoro namespace. Adjust release names and namespaces if your installation uses different values.

​
Upgrade The Hub

Start from the values file used for the existing hub release. If you do not have it locally, export the user-supplied Helm values:
Upgrade the hub chart to 10.4.0:

​
Check The Hub Rollout

Check the hub Helm release and workloads:
If hub self-monitoring is enabled, check the bundled exporter rollout too:
If Metoro AI is enabled, check the Agent Sandbox components:

​
Upgrade Monitored-Cluster Exporters

Upgrading the hub repins future onboarding commands, but it does not automatically upgrade exporter releases already installed on monitored clusters. Repeat this section for every monitored cluster that has metoro-exporter-onprem installed. Start from the values file used for the existing exporter release in the monitored cluster. If you do not have it locally, export the user-supplied Helm values:
Upgrade the exporter chart to 10.4.0:

​
Check Monitored-Cluster Rollouts

After upgrading each monitored cluster, check the exporter Helm release and workloads:
If ServiceMonitor scraping is enabled, check the collector and target allocator rollouts too:
Use the release name and namespace from the existing exporter installation if they differ from the defaults above. Expected outcome:
  • Apiserver and Ingester roll to the 10.4.0 images.
  • Hub self-monitoring rolls to the 10.4.0 exporter chart and images when enabled.
  • Existing monitored-cluster exporter releases roll to the 10.4.0 exporter chart and images after their Helm upgrades.
  • Metoro AI hubs retain the Agent Sandbox controller, router, and Guardian runner defaults when ai.enabled=true.
  • Existing PostgreSQL, ClickHouse, Temporal, and telemetry data remain in place.
  • Future monitored-cluster onboarding commands reference metoro-exporter-onprem 10.4.0.