Cluster Sensor 1.5.0

April 15, 2026 

The Qualys Cluster Sensor 1.5.0 release introduces an enhancement that focuses on providing additional support, improving performance, along with some bug fixes.

Support for Kubernetes Priority Class

Qualys Cluster Sensor 1.5.0 adds support for Kubernetes Priority Class, allowing you to control pod scheduling priority for the cluster sensor. Such pod scheduling is crucial on busy clusters. It also helps in the unnecessary termination (eviction) of the pods.
By default, priority class support is disabled. You can enable it using the Unified Helm Chart (qualys-tc). Once priority classes are set, the Cluster sensor pods are created and assigned the specified priority class.

Support for CIS OKE Benchmark in Oracle Cloud Infrastructure 

Designed for Oracle Cloud Infrastructure (OCI),  the CIS Oracle Kubernetes Engine (OKE) Benchmark offers security-focused configuration guidance for managing and protecting Kubernetes clusters. You can now assess your OKE clusters against the CIS OKE Benchmark, to identify and reduce security misconfigurations.

Support for CPU and Memory Statistics

With this release, Qualys Cluster Sensor collects the CPU and Memory usage of Cluster Sensor container running in your cluster.

Time interval for stat collection is 2 minutes. After every 2 minutes, such stats will be reported in the cluster_sensor.log file.

Issues Addressed

The following issues have been fixed with this release.

Category	Issue
Workload report	Cluster Sensor failed to report a few Cluster resources. To tackle this, Cluster Sensor has added a Watch process to monitor the cluster resources. Such watch process is added for below entities. "Pod", "Namespace", "Node",  "EndpointSlice", "Ingress", "Service", "ServiceAccount"
Inventory scan	Cluster Sensor container crashed due to exeeding memory and CPU limit and threw the following error. OOMKilled Killed process <pid> (java/go/qualys-sensor) total-vm:... Container terminated with exit code 137 (SIGKILL) This issue is fixed by optimizing CPU utilization in the Membrane component to prevent excessive resource consumption.