This article describes how to upgrade an on-premises installation of Cequence App and API Protection (AAP) from release 9.3.x to release 9.4.x, and how to roll back the upgrade. The article is for administrators who manage AAP on Kubernetes using Helm.

Release 9.3.x and release 9.4.x use the same Strimzi release, so this upgrade does not include Strimzi steps. Before you upgrade, read the article about what changes when you upgrade to release 9.4.x. AAP release 9.4.x requires Cequence Defender release 6.5.0 or later.

Upgrade overview

The upgrade has the following stages. Complete the stages in order.

1. Export the AAP configuration.
2. Upgrade AAP to release 9.4.x.
3. Verify the upgrade, then monitor AAP for a few hours.

Before you upgrade

Confirm that you have the following access privileges before you start the upgrade process.

You have helm and kubectl access to the Kubernetes cluster that runs AAP.

You have the Helm override file that you use for AAP.

Exporting the AAP configuration

Export the current AAP configuration before you change anything. When you roll back the upgrade, you import this export to restore the configuration.

Upgrading AAP to release 9.4.x

Upgrade AAP using Helm. During the upgrade, Kubernetes recreates the AAP pods.

1. Upgrade the cequence-asp Helm release to release 9.4.x using your usual Helm upgrade procedure.
2. Watch the pods as Kubernetes recreates them.
3. Verify that every component completes the upgrade.

AAP now runs release 9.4.x.

Verifying the upgrade

After the upgrade, verify that AAP works correctly, and then monitor AAP for a few hours.

1. Verify that all pods are running.
2. Verify that AAP reports release 9.4.x.
3. Verify that the Strimzi CRDs are present and at release 1.2.0.
4. Check the system logs for errors and warnings.
5. For the next few hours, monitor system performance, check the logs for errors or unusual behavior, and verify that all components work correctly.

When AAP shows no errors during the monitoring period, the upgrade is complete.

Rolling back the upgrade

A rollback downgrades AAP and restores the configuration that you exported before the upgrade. Roll back to AAP release 9.3.2 or later, even when you upgraded from an earlier 9.3.x release. Complete the steps in order.

1. Downgrade the cequence-asp Helm release to release 9.3.2 or later using your usual Helm upgrade procedure, and watch the downgrade until every component completes.
2. Verify that all pods are running.
3. Verify that AAP reports release 9.3.2 or later.
4. Check the system logs for errors and warnings.
5. Verify that each configured data export destination receives data.
6. Import the configuration that you exported before the upgrade.

AAP now runs release 9.3.2 or later with the configuration that you exported before the upgrade.