Skip to main content
UAP 8.x Releases

Search

Cequence UAP 8.1.0 upgrade and rollback

© 2024 Cequence Security. All Rights Reserved.

Cequence UAP 8.1.0 upgrade and rollback

  • Updated on
  • ~ minute read
Download PDF

This document describes the process for upgrading your system to the Cequence Unified API Protection (UAP) platform version 8.1.0, which includes upgrading Elasticsearch from version 7.17.21 to 8.18.4. The document also provides rollback instructions to version 8.0.3-ES8 if problems occur during or after the upgrade.

Pre-upgrade requirements

Before starting the upgrade process, confirm the following conditions.

  1. Confirm that your current system runs UAP version 8.0.3.
  2. Have a plan in place to roll back to the 8.0.3-ES8 release.

Upgrade procedure

Follow these steps in order to upgrade your system to UAP 8.1.0.

Export configuration

  1. Export all current system configurations to preserve settings for potential rollback scenarios.

Upgrade ECK operator

  1. Update the ECK operator to version 2.16.1.
  2. From the elastic-system namespace, verify the upgrade by checking pods and deployments.
  3. Confirm the operator image version displays 2.16.1.

SaaS only: enable mixed architecture support

  1. Edit the cluster service configuration to enable ARM/AMD mixed architecture support.

Upgrade UAP to version 8.1.0

  1. Run the Helm upgrade command to install version 8.1.0.
  2. Monitor the upgrade process as the system recreates pods.
  3. Monitor the health of the Elasticsearch cluster during the upgrade process.
  4. Confirm that all components have upgraded successfully.

Post-upgrade verification

  1. Confirm that all pods display a running status.
  2. Confirm that the UAP version displays as 8.1.0.
  3. Confirm the Elasticsearch version displays as 8.18.4.
  4. Confirmthat the Elasticsearch cluster health shows green status.
  5. Review system logs for errors or warnings.

Monitoring period

  1. Monitor system performance for several hours after upgrade completion.
  2. Check error logs for unusual behavior patterns.
  3. Confirm all system components function correctly.
  4. Monitor Elasticsearch performance metrics and resource usage.

Rollback

Use this procedure to roll back to version 8.0.3-ES8, which maintains compatibility with Elasticsearch 8.x.

About version 8.0.3-ES8

Elasticsearch does not support direct downgrades between major versions, such as from version 8.x to 7.x. Rolling back from the 8.1 release of the Cequence UAP to the 8.0 release involves such a downgrade. To work with this issue, use the 8.0.3-ES8 release as your fallback target.

The 8.0.3-ES8 release of the Cequence UAP has the following characteristics.

  • Built on the stable UAP 8.0.3 release foundation.
  • Modified for Elasticsearch 8.x compatibility instead of the original 7.x compatibility.
  • Maintains identical UAP functionality to version 8.0.3 while supporting newer Elasticsearch versions.
  • Serves as a universal rollback target regardless of your starting 8.0.x version (8.0.0, 8.0.1, 8.0.2, or 8.0.3).

This approach enables UAP functionality rollback while maintaining Elasticsearch on version 8.x, along with the improvements that stem from that upgrade.

(SaaS only) Disable mixed architecture support

  1. For SaaS deployments that enabled mixed architecture support during upgrade, disable this feature before proceeding with the rollback.

Downgrade to version 8.0.3-ES8

  1. Run the Helm upgrade command with version specification set to 8.0.3-ES8.
  2. Monitor the downgrade process as components revert to the earlier version.
  3. Confirm that all components complete the downgrade successfully.
  4. Confirm that Elasticsearch remains on version 8.x while becoming compatible with UAP 8.0.3-ES8.

Note: Regardless of your starting 8.0.x version, the system will roll back to version 8.0.3-ES8.

Scale down BA StatefulSet and recreate volume

  1. Scale the BA StatefulSet to zero replicas.
  2. Wait for all pods to terminate completely.
  3. Delete the persistent volume claim associated with the BA StatefulSet.
  4. Scale the StatefulSet to the desired number of replicas.
  5. Monitor pod recreation and initialization processes.

Post-rollback verification

  1. Confirm all pods display a running status.
  2. Verify the UAP version shows 8.0.3-ES8.
  3. Confirm that Elasticsearch remains on version 8.x and functions properly.
  4. Review system logs for errors or warnings.
Was this article helpful?
Japanese (Japan)