Upgrading from 2026.4 to 2026.5.1 (Innovation Release) v1.4.0 (LTS)

Upgrade from 2026.4 to 2026.5.1.

Role: Infrastructure engineer

Prerequisites

• Administrative access to the Kubernetes cluster (kubectl, helm).

• Access to the HM installation configuration file or values.yaml file used for the current installation. To save the contents of your current installation configuration:

  → WrapCopy

  helm get values edbpgai-bootstrap -n edbpgai-bootstrap > values.yaml

• Required tools:

  • helm (Latest version recommended)
  • kubectl
  • edbctl version 1.6.0 or later (or a build from main)

Upgrade 2026.4 → 2026.5.1

HM 2026.5.1 introduces upgrade tooling that automates a complex database migration, including deletion of the stats-collector-db cluster, migration of the edb-observability namespace, and consolidation of app-db, beacondb, and transporter-db into upm-system-db. The tooling runs automatically for both operator and bootstrap helm chart installations via the embedded hmupgrader scripts. No manual data migration steps are required unless an upgrade job fails.

Checking HCP CR annotations

Before upgrading, verify that the HybridControlPlane resource has current-version and previous-version annotations set. The upgrade tooling relies on these parameters to identify which migration scripts to run.

1. Check the currently set annotations:

   → WrapCopy

   kubectl get hcp edbpgai -o yaml | yq '.metadata.annotations | to_entries[] | select(.key | test("edbpgai")) | {.key: .value}'

2. If edbpgai.com/current-version or edbpgai.com/previous-version is missing or empty, set them before proceeding:

   → WrapCopy

   kubectl annotate hcp edbpgai edbpgai.com/current-version=v2026.5.1
   kubectl annotate hcp edbpgai edbpgai.com/previous-version=v2026.4.0

   Replace the version values with the version you are currently running.

Creating new secrets

Before upgrading, create the new secrets required for this release:

edbctl hm create-install-secrets --version v2026.5.1

Performing the upgrade

Once the pre-upgrade steps are complete, initiate the upgrade using the method that matches your installation.

For Helm-based (bootstrap) installations

1. Update your Helm repository:

   → WrapCopy

   helm repo update

2. Run the upgrade:

   → WrapCopy

   helm upgrade --install edbpgai-bootstrap enterprisedb-edbpgai/edbpgai-bootstrap \
     --version 2026.5.1 \
     --values values.yaml \
     --namespace edbpgai-bootstrap \
     --wait

For operator-based installations

1. Update spec.version to v2026.5.1 in your HybridControlPlane manifest and apply it:

   → WrapCopy

   kubectl apply -f hybridmanager.yaml

2. Trigger the upgrade:

   → WrapCopy

   kubectl annotate hybridcontrolplane edbpgai --overwrite edbpgai.com/ready-for-upgrade=true

3. Monitor progress:

   → WrapCopy

   kubectl get hybridcontrolplane edbpgai -w

The operator runs the automated upgrade scripts and applies updated manifests. No additional manual steps are required unless an upgrade job fails.

Troubleshooting upgrade job failures

The upgrade operator creates and manages upgrade jobs automatically. If an upgrade job fails and does not reach a Complete or Succeeded state, the operator pauses and retries. It does not proceed applying updated manifests until the job succeeds.

To investigate a failed upgrade job:

1. Check the status of upgrade jobs:

   → WrapCopy

   kubectl get jobs -n edbpgai-bootstrap -l edbpgai.edb.com/hm-upgrader=true

2. Check the logs for the failed job:

   → WrapCopy

   kubectl logs job/<job-name> -n edbpgai-bootstrap

   Replace <job-name> with the name of the failed job from the previous command.

3. Check the HybridControlPlane status for upgrade-related events:

   → WrapCopy

   kubectl describe hybridcontrolplane edbpgai

If the issue persists after the operator retries, contact EDB support with the job logs.