Upgrade 10.0.2 to 10.1.0 - Metoro Documentation

Metoro 10.1.0 is a minor release in the 10.x on-premises line. It keeps the 10.x Helm values API, so existing 10.0.2 values files can be reused without migration. This release also includes alpha support for running direct PromQL metric queries through a separate PromQL execution engine. No ClickHouse reset, PostgreSQL migration, or additional operational step is required for this upgrade.

These commands assume the Helm release is named metoro and runs in the metoro-hub namespace. Adjust the release name and namespace 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:

helm -n metoro-hub get values metoro > metoro-hub-values.yaml

Upgrade the hub chart to 10.1.0:

helm upgrade --install metoro oci://quay.io/metoro/charts/metoro-onprem \
  --namespace metoro-hub \
  --version 10.1.0 \
  --values metoro-hub-values.yaml

Check The Rollout

Check the Helm release and hub workloads:

helm -n metoro-hub status metoro
kubectl -n metoro-hub rollout status deployment/apiserver
kubectl -n metoro-hub rollout status deployment/ingester

If hub self-monitoring is enabled, check the bundled exporter rollout too:

kubectl -n metoro-hub rollout status deployment/metoro-exporter

Expected outcome:

Apiserver and Ingester roll to the 10.1.0 images.
Hub self-monitoring rolls to the 10.1.0 exporter chart and images when enabled.
Existing PostgreSQL, ClickHouse, Temporal, and telemetry data remain in place.
Future monitored-cluster onboarding commands reference metoro-exporter-onprem 10.1.0.

Upgrade 10.1.0 to 10.2.0Upgrade Metoro on-premises 10.1.0 hubs to 10.2.0

​Upgrade The Hub

​Check The Rollout

Upgrade The Hub

Check The Rollout