> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/readme/documentation-revision-history.md).

# Documentation revision history

Review documentation updates and changes by release.

<table data-first-column-sticky><thead><tr><th width="98.7066650390625">Version</th><th>Description of changes</th></tr></thead><tbody><tr><td></td><td><ul><li><strong>Ethernet and InfiniBand drivers:</strong> Added DOCA 3.5.0 and 3.2.3 as the supported DOCA versions. <a href="/planning-and-installation/prerequisites-and-compatibility.md#ethernet-drivers-and-configurations">>></a></li><li><strong>Supported network adapters:</strong> Added LACP, with load balancing between ports, as a supported feature on CX-8. <a href="/planning-and-installation/prerequisites-and-compatibility.md#networking-ethernet">>></a></li><li><strong>Supported network adapters:</strong> Added NVIDIA BlueField-3 in NIC mode for clients. <a href="/planning-and-installation/prerequisites-and-compatibility.md#supported-network-adapters-for-clients-only">>></a></li><li><strong>Obtain the installation packages:</strong> Updated the download steps for the <strong>Release Lines</strong> tab on get.weka.io. <a href="/planning-and-installation/bare-metal/obtaining-the-weka-install-file.md#download-the-weka-installation-packages">>></a></li><li><strong>Mount filesystems:</strong> Added mounting a filesystem subdirectory instead of the filesystem root, from persistent and stateless clients, and the <code>subdir</code> mount option. <a href="/weka-filesystems-and-object-stores/mounting-filesystems.md#mount-a-filesystem-subdirectory">>></a></li></ul></td></tr><tr><td>6.0.1</td><td><ul><li><strong>Telemetry export health:</strong> Check whether each export delivers audit events from every container. <a href="/operation-guide/audit-and-forwarding-management/manage-audit-and-forwarding-using-the-cli.md#view-telemetry-export-health">>></a></li><li><strong>Data Services:</strong> The configuration filesystem requires at least 50 GiB. <a href="/operation-guide/set-up-a-data-services-container-for-background-tasks.md">>></a></li><li><strong>Asynchronous replication:</strong> Added the cross-cluster replication license prerequisite. <a href="/weka-filesystems-and-object-stores/asynchronous-replication/manage-asynchronous-replication.md#prepare-the-clusters-for-replication">>></a></li><li><strong>Asynchronous replication:</strong> Clarified inode numbers on the target and how to make the target filesystem writable. <a href="/weka-filesystems-and-object-stores/asynchronous-replication.md#considerations">>></a></li><li><strong>Asynchronous replication:</strong> One <code>weka cluster link add</code> command links both clusters, and replication needs no bucket, S3 user, or object store filesystem. <a href="/weka-filesystems-and-object-stores/asynchronous-replication/manage-asynchronous-replication.md#link-the-clusters">>></a></li><li><strong>CLI reference guide:</strong> Added <code>weka cluster link</code> and the <code>weka replication</code> command group. <a href="/getting-started-with-weka/weka-cli-overview/cli-reference-guide/weka-replication.md">>></a></li></ul></td></tr><tr><td>6.0</td><td><ul><li><strong>New WEKA CLI (wekactl)</strong>: Manage clusters from any supported platform using a new <code>weka</code> CLI (formerly <code>wekactl</code>), a modern command-line interface. <a href="/getting-started-with-weka/weka-cli-overview.md">>></a></li><li><strong>Asynchronous replication</strong>: Protect your data with asynchronous replication, which synchronizes filesystems directly between two clusters. <a href="/weka-filesystems-and-object-stores/asynchronous-replication.md">>></a></li><li><strong>NFS multi-tenancy</strong>: Give tenants NFS access without installing a client. Each tenant gets isolated client groups and exports, reached through dedicated floating IP addresses in its own network space. Kerberos, ACLs, NFS group resolution through LDAP, and NFSv3 locking remain available only in the root organization, and tenant mounts use <code>sec=sys</code> with numeric UIDs and GIDs. <a href="/operation-guide/weka-native-multi-tenancy-management/manage-nfs-for-tenants.md">>></a></li><li><strong>SMB external LDAP POSIX resolution</strong>: Resolve SMB POSIX user and group attributes from an external LDAP directory, separately from the domain used for authentication. <a href="/additional-protocols/smb-support/smb-external-ldap-posix-resolution.md">>></a></li><li><strong>Diagnostics data management</strong>: Manage diagnostics data for clusters, servers, and containers from the CLI, including collection, listing, and removal. <a href="/support/diagnostics-management/diagnostics-data-management.md">>></a></li><li><strong>Traces debug level management</strong>: Set and inspect trace debug levels alongside the protocols debug levels, from either the CLI or the GUI. <a href="/support/diagnostics-management/traces-and-protocols-debug-level-management.md">>></a></li><li><strong>Breaking changes</strong>: Review the changes that take effect immediately after upgrading, including six NFS CLI subcommands renamed from <code>delete</code> to <code>remove</code> (the legacy spellings are kept as aliases), tightened role requirements on five NFS API endpoints, and renamed JSON output keys. <a href="/operation-guide/upgrading-weka-versions/breaking-changes.md">>></a></li><li><strong>View alerts as a tenant</strong>: Cluster administrators can view the alert list as it appears to a specific tenant admin, without logging in as that user. This helps when investigating alert visibility discrepancies in multi-tenant clusters. <a href="/operation-guide/weka-native-multi-tenancy-management/multi-tenancy-cluster-level-administration.md#view-alerts-as-a-tenant">>></a></li><li><strong>GUI updates</strong>: Explore the refreshed management UI with a new look and feel. <a href="/getting-started-with-weka/manage-the-system-using-weka-gui.md">>></a></li></ul></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/readme/documentation-revision-history.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.