Overview

Metoro releases for self-managed deployments are distributed as versioned Helm charts. Each major release line has its own chart API, documentation, and upgrade expectations.

​

Release Lines

Metoro uses the major version as the compatibility line for self-managed deployments. For example, 10.x is the release line for the standalone metoro-onprem chart. Within a major release line, minor and patch releases are expected to be upgradeable without rewriting your values files. These releases may include application upgrades, fixes, chart fixes, default tuning changes, dependency updates, and other compatible improvements. Major upgrades can change chart values, architecture, bundled dependencies, or operational requirements. When a major upgrade requires migration work, Metoro documents that path separately instead of treating it as a routine patch upgrade.

​

Version Pinning

Install and upgrade Metoro with explicit chart versions, such as 10.1.0. Do not rely on floating tags or unpinned chart references for production deployments. The hub chart pins the compatible pieces of the deployment:

• the metoro-onprem hub chart version
• the compatible metoro-exporter-onprem chart used for hub self-monitoring and monitored-cluster onboarding
• Metoro application image tags
• bundled dependency chart versions and default dependency images

This means a chart version represents the tested release unit. Override image tags or dependency versions only when Metoro support tells you to do so.

​

Documentation Versions

Use the documentation that matches your major release line:

• 10.x is the canonical path for new standalone installs.
• 9.x preserves the previous chart documentation for existing legacy deployments.
• 8.x and older deployments should be upgraded with Metoro support guidance.

When in doubt, start with your installed metoro-onprem chart version. The major version determines which documentation line applies.