Upgrading 6.2.0 → 6.2.1 (introduced in v6.2.1)

important

When upgrading to 6.2.1, ensure that your StorageClass name matches the 6.2.0 deployment and that volumeBindingMode is set to WaitForFirstConsumer. This is because the volumeClaimTemplates field in a logcollector StatefulSet (which includes storageClassName) is immutable and cannot be changed after creation.

For example, if your cloud provider is GKE, then the built-in StorageClass should be standard-rwo, and volumeBindingMode should be WaitForFirstConsumer.

Steps to upgrade

note

Before you begin, ensure the Boomi Cloud API Management - Local Edition 6.2.0 cluster is up and running.

Procedure

1. Build new images.

   Refer to Building Images for more information.

2. Upgrade cluster using Helm. Run the following command:

   
   $ helm upgrade apim deploy  --namespace <namespace name> 
   --set preInstallDBPrep.initDBUserPassword= \ 
   --set preInstallDBPrep.localDevAdminPassword=
   
   The expected sample output is as follows:
   
   NAME: apim
   LAST DEPLOYED: Fri Oct 13 08:01:54 2023
   NAMESPACE: <namespace_name>
   STATUS: deployed
   REVISION: 2
   TEST SUITE: None
   

tip

If you are facing any issues upgrading to 6.2.1, consider rolling back to 6.2.0.

Refer to Rollback 6.1–6.2.x → previous 6.x for more information.