> For the complete documentation index, see [llms.txt](https://documentation.alluxio.io/k8s-operator-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alluxio.io/k8s-operator-en/release-notes/operator-3-4-0.md).

# Alluxio Kubernetes Operator 3.4.0 Release Notes

## Summary

### New Features

* **FoundationDB integration** lets the Operator deploy and manage FoundationDB for Alluxio capabilities that require it.
* **License lifecycle management** lets you manage Alluxio Enterprise licenses through the Operator.
* **Non-disruptive FUSE upgrades** reduce interruption when FUSE clients are upgraded; failed FUSE pods are retained for diagnosis.

### Major Enhancements

* **Storage and client configuration** is more flexible: you can update UFS mount options, and Worker deployment supports the Python SDK.
* **Diagnostics** produce more consistent collection content and layout.
* **Kubernetes integration** now uses the Kubernetes staging path by default instead of a static path.

## Breaking Changes

* You can no longer use Alluxio releases earlier than AI 3.5 because this Operator version requires the newer coordinator API.
* The Helm chart no longer creates the `alluxio-operator` namespace for you.
* For AI 3.8 deployments, Workers use StatefulSets and their default identity is the pod name.
* FUSE mount locations now use a subdirectory under `/var/lib/kubelet/`; the former `/mnt/alluxio/fuse-<pv-id>` path is no longer created.

## Upgrade Notes

* Create the target namespace before you install or upgrade the Operator.
* Verify that your Alluxio version is supported, and update automation that depends on the former Worker identity or FUSE mount path.
* After upgrading, validate FUSE-backed workloads, especially those that reference the former mount location.