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 provides visibility into the CPU and memory usage of the CPU and Memory usage of Cluster Sensor container running in your cluster. This usage statistics are collected and reported every 2 minutes in the Cluster Sensor logs. By monitoring sensor resource consumption, you can ensure that the Cluster Sensor has sufficient CPU and memory, reducing the risk of 'OOMKilled' events or unexpected restarts.
The 2‑minute reporting interval enables you to quickly identify memory consumption spikes and proactively manage resource allocation.

Unified Helm Chart (qualys-tc 2.8.0) Updates

The unified helm chart can be used to install QCS Sensor, Admission Controller, Cluster Sensor, and Container Runtime Sensor.
Refer to Qualys Unified Helm Chart (qualys-tc).

Enhancements to Cluster Sensor values.yaml in qualys-tc

With this release, the following flag is introduced in the 'qualys-tc 2.8.0' file.  

Flag/Entity	Status	Flag Location (qualys-tc > charts > cluster sensor > values.yaml)	Description
priorityClass: enabled: true name: "cluster-low" #priority class name used in cluster sensor deployment value: 1000000 #value determines the priority e.g. 1000000 preemptionPolicy: "Never" #preemption policy for pod	New	Line No. 32 to 36	To specify the priority class of Cluster sensor.

Issues Addressed

The following issues have been fixed with this release.

Category	Issue
Workload report	Cluster Sensor failed to report a few Cluster resources. Now, Cluster Sensor has added a resource version-based tracking to monitor the cluster resources.
Inventory scan	Cluster Sensor container crashed due to 'OOMKilled' error on large cluster. This is fixed by optimizing Memory utilization which prevents excessive resource consumption.