v1.1.0

Dependencies

Glasswall Halo v2.4.3

Glasswall Halo Services (Image Tags)

Glasswall Halo Helm Chart Versions

Service Versions (Image Tags)

Helm Chart Versions

New Features

• Security updates have been applied to all Constellations services, guaranteeing that each dependency aligns with its latest recommended and secure versions.

Updated Glasswall Halo

• Constellations has been upgraded to harness the capabilities of the latest Glasswall Halo release. This updated version incorporates bug fixes and also integrates essential security enhancements, such as:
  • An extensive enhancement to the core of our CDR technology—the embedded engine, is unveiled with Release 5.
    • Please note, this includes updates to the licensing functionality. For more information, please contact us.
  • We have introduced a significant improvement in the handling of file cleanup - please see Glasswall Halo v2.2.0.
  • Updates in archive file handling have been implemented to enhance performance and resilience. Refer to Glasswall Halo v2.2.1 for details.
  • We've implemented a significant security enhancement: all Glasswall assets pertaining to Halo code and deliverables, including container images, are now signed by default. This ensures an added layer of trust and authenticity in our system.

Known Issues

• Issue: In the event of a dead-letter on the cdr-enablement queue, the GET Scan Summary endpoint response may show a lower value for numberOfProcessedFiles compared to numberOfFiles.
  • Impact: This discrepancy can lead to confusion regarding the actual number of files processed during a scan.
• Issue: For scans marked as Errored, the status response may return a null value for ScanEndTime.
  • Impact: The absence of a valid ScanEndTime can hinder accurate tracking and analysis of scan durations for errored scans.
• Issue: The constellations-scan-preprocessor service may encounter errors while attempting to write to the FileMetadata Cosmos container, resulting in duplicate cdr-enablement messages. As a consequence, individual files may be processed multiple times.
  • Impact: Duplicate file processing can lead to resource utilisation inefficiencies and potential delays in overall scan completion.
• Issue: When Constellations encounters an archive in a source container during autoscaling, only one new pre-warmed cdrplatform-engine pod will scale up.
  • Impact: This behaviour can introduce a slight processing delay for archives, as additional scaling of cdrplatform-engine pods is contingent on the engine-requests queue in the CDR Platform.
• Issue: When restarting your cluster, a timing issue with the deployment of RabbitMQ can cause the Constellations services to hang, and not fail their liveness probes.
  • Impact: This can lead to confusion after a cluster-wide restart. The problem can be solved by restarting all pods in the following namespaces: scan-management, cdr-enabler and event-collation.

Documentation

API Documentation

Constellations Documentation