Upgrading from 1.3.x to 1.3.7 v1.3.8 (LTS)

Role: Infrastructure Engineer

Prerequisites:

• Administrative access to the Kubernetes cluster.
• Access to the values.yaml file used for the current installation.
• Required tools:
  • helm (Latest version recommended)
  • kubectl

Upgrade from 1.3.x → 1.3.7

Delete the stats-collector-db cluster

Before upgrading, you must delete the stats-collector-db cluster. This step is mandatory.

The upm-api-stats-collector component now uses an updated extension version to address a critical write-ahead log (WAL) file issue. Because existing data in this cluster can't be migrated, you must delete it before proceeding with the upgrade.

1. Delete the cluster:

   → WrapCopy

   kubectl -n upm-api-stats-collector delete cluster stats-collector-db

   If the deletion hangs, force a hard delete by removing the pods:

   → WrapCopy

   kubectl -n upm-api-stats-collector delete pod stats-collector-db-1 --force

2. Verify that the following resources are no longer present before proceeding:

   → WrapCopy

   kubectl -n upm-api-stats-collector get cluster stats-collector-db
   kubectl -n upm-api-stats-collector get pod stats-collector-db-1
   kubectl -n upm-api-stats-collector get pvc stats-collector-db-1

   Each command should return a "not found" response.

Perform the upgrade

helm repo update

helm upgrade --install edbpgai-bootstrap enterprisedb-edbpgai/edbpgai-bootstrap \
   -n edbpgai-bootstrap \
   -f ./values.yaml \
   --version 1.3.7