# Version 5.2.X Release Highlights

## Version 5.2 of Trilio for Kubernetes introduces major new capabilities as follows

## 5.2.0

#### ✨ New Features

* **Namespace Label Restoration**: Added support to restore namespace labels during recovery. Any labels present on namespaces at the time of backup can now be restored on the restore namespaces.
* **Topology Spread Constraints Support**: Introduced support for topology spread constraints, allowing users to control how Pods are distributed across failure domains such as regions, zones, nodes, or other custom topology domains for improved resource utilization.
* **Configurable S3fuse Worker Threads**: The number of S3fuse worker threads used during S3-based backup and restore operations is now configurable. Each worker thread uses multipart uploads and can open up to four concurrent upload sessions.

#### 🐞 Bug Fixes

* **Stricter S3 Target Validation**: Enhanced S3 target validation with stricter permission and API checks. Target validation will now fail if any required S3 operation is not permitted.
* **BackupPlan Resource Selection**: Fixed an issue in the UI that prevented users from including resources with non-preferred API versions during BackupPlan creation.
* **VM Restore with ConsistentSet**: Resolved an issue where virtual machines failed to boot after restore when using a ConsistentSet.
* **PVC Annotation Handling in VM Restore**: Fixed a VM restore failure caused by retaining PVC annotations introduced in T4k release 5.1.2.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.trilio.io/kubernetes/5.2.x/about-trilio-for-kubernetes/release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.