Upgrading from 1.4.3 to 1.4.4 v1.4.4 (LTS)

Role: Infrastructure engineer

Prerequisites

• Administrative access to the Kubernetes cluster.
• Required tools:
  • helm (latest version recommended)
  • kubectl
  • edbctl, the Hybrid Manager CLI — see the edbctl compatibility matrix for the supported version.

Upgrade 1.4.3 → 1.4.4

Create new secrets

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

edbctl hm create-install-secrets --version v1.4.4

For more CLI options, see edbctl hybrid-manager. To customize your component's secrets, see Customizing secrets.

Upgrade the operator

The commands below use edb-hcp-operator-system — use the namespace where your operator is actually installed. If you migrated from the bootstrap method, the conversion transfers Helm ownership onto edbpgai-bootstrap, so use that namespace instead.

Upgrade the edb-hcp-operator Helm chart using edbctl:

edbctl hm upgrade-operator \
  --release-name edb-hcp-operator \
  --namespace edb-hcp-operator-system \
  --registry-uri docker.enterprisedb.com/pgai-platform \
  --registry-username pgai-platform \
  --registry-password <password>

Or upgrade directly with Helm:

1. Create the values file:

   → WrapCopy

   cat <<EOF > edb-hcp-operator.values.yaml
   controllerManager:
     manager:
       image:
         repository: docker.enterprisedb.com/pgai-platform/edb-hcp-operator/manager
         tag: <OPERATOR_VERSION>
   imagePullSecrets:
     - name: edb-cred
   EOF

2. Run the upgrade:

   → WrapCopy

   helm upgrade --install \
     --version <OPERATOR_VERSION> \
     --values edb-hcp-operator.values.yaml \
     -n edb-hcp-operator-system \
     edb-hcp-operator enterprisedb-edbpgai/edb-hcp-operator

Review your spec.scenarios list

If your operator is still on 2.1, upgrading it to 2.2 changes what happens when spec.scenarios is omitted from your HybridControlPlane manifest. Operator 2.1 fills an empty list with the full default set: core, dbaas, ai, analytics, migration, and marketplace. Operator 2.2 installs only core.

Before you upgrade, read back the scenarios currently applied to your deployment:

kubectl get hybridcontrolplane <name> -o jsonpath='{.spec.scenarios}'

Add the returned scenarios to spec.scenarios in your manifest so the list is explicit before you bump spec.version. For details, see Choosing an installation scenario.

Upgrade Hybrid Manager

1. Update spec.version to v1.4.4 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