From version 2.0.0, the Hybrid Manager (HM) operator is released independently of HM, with its own versioning lifecycle. Its version numbers don't mirror those of HM.
A single 2.x operator supports a range of HM versions, across both the long-term support (LTS) and innovation release (IR) lines.
The following matrix gives the minimum operator version each HM version needs.
| HM versions | Minimum operator version | Notes |
|---|---|---|
| 2026.9 (IR) | 2.2.0 | Required for the pgd scenario. |
| 1.4.2, 1.4.3 (LTS), 2026.8 (IR) | 2.1.0 | Required for the marketplace scenario. |
| 1.4.0, 1.4.1 (LTS), 2026.7 (IR) | 2.0.0 | First release with independent operator versioning. |
Scenarios and required operators
Some scenarios are recognized only from a given operator version onward. Bring the operator to that version before you add the scenario to spec.scenarios.
pgdrequires operator 2.2.0 or later. HM 2026.9 moves the components that manage Postgres Distributed (DHA) clusters out ofcoreand into apgdscenario. Operator 2.1.0 doesn't recognize the value, so upgrade the operator to 2.2.0 or later, then addpgdtospec.scenarios, and only then bumpspec.version— the order is important, otherwise those components are removed along with the data the clusters hold.marketplacerequires operator 2.1.0 or later. HM 1.4.2 and 2026.8 add amarketplacescenario, covering kapp-controller and the OSS Library apps it deploys. Operator 2.0.0 doesn't recognize the value and silently drops it from your manifest rather than reporting an error, so bring the operator to 2.1.0 or later before you add the scenario, and read the resource back to confirm it persisted.