Title
Create new category
Edit page index title
Edit category
Edit link
Release notes
Version | 2.8.0 |
|---|---|
Release date | 30 July 2026 |
Scope | MetaDefender Cluster 2.8.0 introduces major enhancements for cloud-native deployment and operations. This release adds Kubernetes support with high availability, rolling upgrades, and Terraform-based infrastructure provisioning, making it easier to deploy and manage MetaDefender Cluster across modern cloud environments. In addition, the release strengthens platform security and operational reliability through TLS support for infrastructure services, improved container resource monitoring, updated third-party libraries, and numerous stability improvements and bug fixes. |
New Features, Improvements and Enhancements
Cloud-native deployment
Kubernetes deployment
MetaDefender Cluster can now be deployed and operated on Kubernetes, enabling scalable, cloud-native deployments across modern infrastructure.
High availability
MetaDefender Cluster now supports high-availability deployments on Kubernetes, with HA deployment options for PostgreSQL, RabbitMQ, Redis and MetaDefender Cluster File Storage.
Staged upgrades
MetaDefender Cluster now supports staged upgrades through separate Helm charts for platform services and worker instances, reducing service disruption during upgrades.
Official Docker images
Official Docker images are now available for all MetaDefender Cluster services, simplifying containerized deployments.
Graceful worker shutdown
MetaDefender Cluster Worker instances running on Kubernetes now complete in-progress processing before shutting down, helping prevent interrupted scans during scaling and upgrades.
Infrastructure as Code (IaC)
Terraform deployment
Infrastructure as Code (IaC) support has been introduced using Terraform, allowing consistent deployment of MetaDefender Cluster across AWS, Microsoft Azure, and Google Cloud Platform. Production-ready Terraform templates are included to simplify provisioning and deployment.
Further Enhancements
1. Better resource monitoring inside containers
System resource monitoring is now cgroup-aware. When running inside Docker or Kubernetes, MetaDefender Cluster correctly reports container CPU and memory limits instead of host machine resources, resulting in more accurate monitoring and resource management.
2. Improved connection reliability
Long-running PostgreSQL, Redis, RabbitMQ and MetaDefender Cluster File Storage operations are now better protected against idle network timeouts, improving stability when firewalls or load balancers are present.
Security Enhancements
Long-running PostgreSQL, Redis, RabbitMQ and MetaDefender Cluster File Storage operations are now better protected against idle network timeouts, improving stability when firewalls or load balancers are present.
Several bundled components have been updated to improve security, stability, and compatibility, including:
PostgreSQL 18
NGINX 1.30.4
OpenSSL 3.5.7
SQLite 3.53.3
7-Zip 26.02
yaml-cpp 0.9.0
nghttp2 1.69.0
Angular 20.x
RESTful API
A new GET
/readyzendpoint is available to allow Kubernetes and external orchestration systems to determine whether a service is ready to receive traffic.
Bug Fixes
Fixed an issue where the GET
/fileAPI incorrectly returned 404 Not Found for files scanned by users that had later been deleted. The API now returns the scan result with an empty user field.
Known Limitations
MD Cluster Control Center does not detect duplicate workers when one is added using its IP address and another using its hostname (or vice versa). Registering the same worker multiple times may lead to incorrect license usage calculations.