EDB Docs - Hybrid Manager operator v2 - Hybrid Manager operator 2.0.0 release notes

Released: 04 June 2026

Version 2.0.0 is the first Hybrid Manager (HM) operator release with its own version number and its own release cadence, separate from HM.

Highlights

The operator is now released independently of HM. The operator has its own version number and its own release cadence, so you can pick up operator fixes and improvements without waiting for an HM release. A single 2.x operator supports a range of HM versions — see the compatibility matrix.
The bootstrap and edbpgai-bootstrap Helm charts are deprecated. Installing HM through either chart is no longer supported. Migrate to the unified HM Helm chart.
Private and air-gapped registries are easier to work with. You can trust a custom CA for kapp-controller, install an in-cluster container registry through the operator Helm chart, and point the operator at an HM Registry.

Description
Configurable `kapp-controller` TLS trust You can set a custom CA certificate trust, or disable TLS verification, for private container registries. The setting is exposed both on the operator Helm chart and on the `HybridControlPlane` custom resource.
Optional in-cluster container registry The operator Helm chart can now install an in-cluster container registry, which removes the need for an external registry in disconnected environments.
Support for HM Registry The operator can source images from an HM Registry, and `HybridControlPlane` resources are integrated with it.
Support for pre-upgrade and post-upgrade jobs You can run jobs before and after an upgrade. The upgrade job can be skipped, and it can be run more than once.
`componentsParameters` is available during Helm chart rendering Component parameters are included in the Helm chart render and expansion context, so component values can be templated from the `HybridControlPlane` resource.
Custom load balancer annotation support You can set your own annotations on the load balancers the operator creates.
Support for AKS, MicroK8s, and NKP The operator adds platform flavors for Azure Kubernetes Service (AKS), MicroK8s, and Nutanix Kubernetes Platform (NKP), alongside the existing platforms.

Description
Managed resources are labeled `pgai.enterprisedb.com/system` Every resource the operator manages carries the `pgai.enterprisedb.com/system` label, and the operator namespace is labeled as a PGAI system namespace, which makes operator-owned resources easier to identify and select.

Description
The operator is versioned and released independently of Hybrid Manager The operator no longer shares a version number or a release cadence with HM. A single `2.x` operator supports a range of HM versions, so upgrading the operator and upgrading HM are now separate operations. Run `edbctl hm upgrade-operator` to move to the latest operator available in your registry, then set `spec.version` in your `HybridControlPlane` manifest to choose the HM version. The operator also now enforces the remote method for operations, overriding any locally specified methods, so that cluster management behaves consistently.
The portal domain is configured with `portal_domain_name` The operator uses `portal_domain_name` to configure the portal domain, instead of deriving it from the `trust_domain` parameter. The trust domain is configured separately, and additional allowed trust domains can be set through the values file.
`prometheus-operator` can be disabled when it's already installed Where the target platform already provides `prometheus-operator`, the component can now be disabled outright rather than only having its CRDs annotated to avoid conflicts.

Description
The `bootstrap` and `edbpgai-bootstrap` Helm chart installation methods are deprecated Action required. Both charts are deprecated in favor of the unified HM Helm chart. See Migrating from bootstrap to the HM operator.