Upgrading from 1.4.2 to 1.4.3 v1.4.3 (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.2 → 1.4.3

Create new secrets

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

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

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

Migrate a customized Velero backup schedule

Starting in HM 1.4.3, the Velero backup schedule configuration moves from the upm-velero component to upm-velero-config.

If you set schedule under spec.componentsParameters.upm-velero in your HybridControlPlane manifest, move that value to upm-velero-config before you upgrade.

If you haven't customized the backup schedule, no action is needed. For details, see Changing the default backup schedule.

Upgrade Hybrid Manager

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