To install the Cequence Unified API Protection (UAP) platform on a shared cluster, you need to verify two prerequisites: whether Elastic Cloud on Kubernetes (ECK) is installed with a compatible version, and whether Strimzi is installed with a compatible version.
This article explains why these requirements exist, what happens when versions don't align, and guidance for selecting the actions you need for a successful Cequence UAP platform installation.
Why ECK and Strimzi are required
The Cequence UAP platform uses two core infrastructure components that require orchestration on Kubernetes:
- Elasticsearch stores and indexes API security events, alerts, and logs that the Cequence UAP platform generates during operation.
- Kafka handles event streaming, allowing the Cequence UAP platform to process API traffic signals and threat intelligence in real time.
ECK is the Kubernetes operator that manages Elasticsearch clusters. Strimzi is the Kubernetes operator that manages Kafka clusters. Both operators handle lifecycle management, resource allocation, scaling, and failover for their respective components.
Why specific versions are required
The Cequence UAP platform has hard dependencies on specific versions of Elasticsearch and Kafka. These versions have been tested and validated to work with the Cequence UAP platform's features and security model. Using untested or incompatible versions means the Cequence UAP platform will not install or run.
Because only one ECK operator and one Strimzi operator can run on a shared Kubernetes cluster, your cluster's current ECK and Strimzi versions must be compatible with what Cequence UAP platform requires. If your current versions fall outside the supported ranges shown below, you must change them before proceeding with Cequence UAP platform installation. This might mean upgrading to a newer version or downgrading to an older one, depending on your cluster's current state.
If you cannot switch your cluster's ECK or Strimzi to a compatible version, you cannot install the Cequence UAP platform on that cluster.
Supported versions
The Cequence UAP platform uses Elasticsearch 8.18.4. The following table shows which ECK operator versions support this Elasticsearch release:
| ECK operator version | Elasticsearch support | Notes |
| 3.1.0+ | 7.17+, 8.x, 9.x | Latest version, supports Elasticsearch 8.18.4 |
| 3.0.0–3.0.x | 7.17+, 8.x, 9.x | Supports Elasticsearch 8.18.4 |
| 2.16.1 | 6.8+, 7.1+, 8+ | Latest 2.x patch, supports Elasticsearch 8.18.4 |
| 2.16.0 | 6.8+, 7.1+, 8+ | Supports Elasticsearch 8.18.4 |
| 2.15.0 | 6.8+, 7.1+, 8+ | Supports Elasticsearch 8.18.4 |
| 2.14.0–2.14.x | 6.8+, 7.1+, 8+ | Supports Elasticsearch 8.18.4 |
| 2.0.0–2.13.x | 6.8+, 7.1+, 8+ | All 2.x versions support Elasticsearch 8.18.4 |
| 1.9.0–1.9.x | 6.8+, 7.1+ | Older versions still compatible with Elasticsearch 8.x |
| 1.6.0–1.8.x | 6.8+, 7.1+ | Older versions still compatible with Elasticsearch 8.x |
The Cequence UAP platform uses Kafka 3.7. The following table shows which Strimzi operator versions support Kafka 3.7:
| Strimzi version | Kafka version | Notes |
| 0.44 | 3.7.1 | Latest version to support Kafka 3.7 |
| 0.43 | 3.7.1 | |
| 0.42 | 3.7.1 | |
| 0.41 | 3.7.0 | First Strimzi version to support Kafka 3.7 |
| 0.40 | 3.7.0 |
Checking your cluster's current versions
Before installing the Cequence UAP platform, verify which ECK and Strimzi versions your cluster currently has. The procedures for checking operator versions are outside the scope of this guide; consult your cluster administrator or your Kubernetes platform's documentation.
Once you know your current versions, compare them to the supported versions shown above. If your cluster's ECK version falls within the supported range and your Strimzi version falls within the supported range, you can proceed to install the Cequence UAP platform.
What to do if your versions are incompatible
If your cluster has ECK or Strimzi versions that are not in the supported ranges above, you must upgrade or downgrade those operators before installing the Cequence UAP platform.
Changing operator versions on a shared cluster can affect workloads that depend on those operators. Plan this change carefully and coordinate with your cluster administrators and any teams running Elasticsearch or Kafka workloads on the cluster. Test the operator version change in a non-production environment first if possible.
Once you have changed your operators to supported versions, you can proceed with Cequence UAP platform installation.
How compatible versions affect your installation procedure
During Cequence UAP platform installation, you will encounter sections that guide you through installing ECK and Strimzi operators. If your cluster already has compatible versions of these operators installed, skip those installation sections entirely. Installing the operators again could cause conflicts or unexpected behavior.
If your cluster does not yet have ECK or Strimzi installed, follow those installation sections to deploy the operators, then proceed with Cequence UAP platform installation.