This topic provides information about the technical support for the StackRox Kubernetes Security Platform and details about other supported software and infrastructure.
|
StackRox supports the StackRox Kubernetes Security Platform versions for up to six months after its release, which corresponds to the previous nine released versions. StackRox will make reasonable efforts and assist you in supporting some older versions. However, the support team may request you to upgrade to a newer released version of the StackRox Kubernetes Security Platform for full support.
For the StackRox Kubernetes Security Platform, StackRox supports:
The support window of the StackRox Kubernetes Security Platform versions is known as N-9 where: N (latest release) - 9 (earlier versions). Along with our N-9 support window, StackRox might support version N-10 to N-13, depending on a case-by-case basis. StackRox will not support any earlier versions than N-13. |
The StackRox support team supports a platform version based on the upstream (or vendor) product’s support lifecycle for that version. When support for a platform version reaches its end of life (EOL) or is not actively maintained, StackRox no longer supports it.
StackRox does not support:
|
Operating system | Version |
---|---|
16.04 LTS, 18.04 LTS, and 20.04 LTS with standard or cloud-provider-specific kernel versions |
|
9, 10 |
|
7.3 till 7.9, 8.0 and newer |
|
7, 8 |
|
Stable stream 32.20200824.3.0 and newer |
|
2023.4.0 and newer |
|
77 and newer |
|
2 |
|
27.0 and newer |
Container runtimes | Version |
---|---|
17.03 and newer |
|
- |
CRI-O and runC support is available starting from Red Hat Advanced Cluster Security for Kubernetes version 2.5.31.0. |
Container orchestrators and platforms | Version |
---|---|
1.15 and newer |
|
3.10, 3.11, 4.1, and newer |
|
2.0.0 and newer |
|
StackRox support recent Kubernetes and OpenShift Container Platform versions, and test on managed Kubernetes service from all major cloud providers, including:
To install Collector on GKE clusters that have secure boot enabled, you must use eBPF probes because the third-party unsigned kernel module, unsigned by Google’s CA, cannot be loaded when secure boot is enabled. Collector identifies Secure Boot status at the start and switches to eBPF probes if required. |
Along with other types of clusters, StackRox also supports clusters created by using the kops - Kubernetes Operations tool with the default configurations on Amazon Web Services (AWS).