Release 1.44.2

August 03, 2026

- Qualys strongly recommends upgrading your Qualys Container Security Sensor to 1.44.2 version to avail the latest features and enhancements.
- Ensure that you also update your existing Sensor Deployment Yaml files with the latest Yaml files published with 1.44.2 release.

Added Support for Custom Labels for qcs-sensor

With this release, you can install the Qualys Sensor with custom labels for the qualys-container-sensor pod. The following sections describe two methods for installing the QSC Sensor using Unified Helm Chart 2.10.0 and the values.yml file. You can use either method based on your deployment requirements.

Usage: --set qcsSensor.podlabels.CustomLabelKey=CustomLabelValue

Alternatively, you can also add above flags in values.yaml.
podlabels:
CustomLabelKey: "CustomLabelValue"

Refer to the Unified Helm Chart (qualys-tc 2.10.0) Updates to know the locations of above flags.

Unified Helm Chart (qualys-tc 2.10.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

With this release, the following flag is updated in the 'qualys-tc 2.10.0' file.

Flag/Entity	Status	Flag Location (qualys-tc > charts > qcs-sensor > values.yaml)	Description
podlabels	New	163	Add custom labels to qcs sensor

Helm Chart 1.23.0 Updates

The Qualys Container Security package consists of the 'values.yaml' file, which deploys the sensor in various environments.
This section explains the updates in the latest Helm chart (values.yaml) file. Refer to QCS Sensor Helm Chart (qcs-sensor).

Enhancements

With this release, the following flags are introduced or updated in the 'values.yaml' file.

Flag/Entity	Status	Flag Location in YAML 1.23.0	Description
podlabels	New	163	Add custom labels to qcs sensor

Issues Addressed

The following issues have been fixed with this release.

Category Issue

Image Scanning in GKE with GCFS

Category	Issue
Image Scanning in GKE with GCFS	Fixed an issue where image scans could fail in Google Kubernetes Engine (GKE) environments when the Google Container File System (GCFS) mount path was changed in the latest GKE version. Previous Configuration: `- mountPath: /run/gcfsd/mnt/layers name: gcfs-layers readOnly: true` Updated Configuration: `- name: gcfsd-mount mountPath: /run/gcfsd readOnly: true` The warning displayed when the mountpath is missing: `[qpa-1.44.2-0][8]:[Warning]:[7bd8ad0780c0] gcfs mount path /run/gcfsd is not mounted (ReadOnly). If this path exists on the host, it must be mounted as ReadOnly in the sensor DaemonSet. Without this mount, image scans will fail when GKE uses symlinks under /run/gcfsd to reference image layers.`
Activity Tracker and Task Runner	Fixed an issue where Activity Tracker and Task Runner failed to use the system-detected proxy, resulting in the error "`proxyconnect tcp: dial tcp :0: connect: connection refused`".
Task Runner	Fixed an issue where log archive generation could fail with a "write too long" error. This occurred when sensor logs were updated during archive creation.

Fixed an issue where image scans could fail in Google Kubernetes Engine (GKE) environments when the Google Container File System (GCFS) mount path was changed in the latest GKE version.

Previous Configuration:

- mountPath: /run/gcfsd/mnt/layers

			  name: gcfs-layers

			  readOnly: true

Updated Configuration:
- name: gcfsd-mount mountPath: /run/gcfsd readOnly: true

The warning displayed when the mountpath is missing:
[qpa-1.44.2-0][8]:[Warning]:[7bd8ad0780c0] gcfs mount path /run/gcfsd is not mounted (ReadOnly). If this path exists on the host, it must be mounted as ReadOnly in the sensor DaemonSet. Without this mount, image scans will fail when GKE uses symlinks under /run/gcfsd to reference image layers.

Activity Tracker and Task Runner Fixed an issue where Activity Tracker and Task Runner failed to use the system-detected proxy, resulting in the error "proxyconnect tcp: dial tcp :0: connect: connection refused".

Task Runner Fixed an issue where log archive generation could fail with a "write too long" error. This occurred when sensor logs were updated during archive creation.

Last updated: August, 2026