# Longhorn v1.12.2

> Storage & Data · 2026-11-09

A stability-focused maintenance release addresses data-loss risks, panics, deadlocks, mount delays, device-state handling, and defects across both data engines. It also improves networking and Helm charts, with upgrade prerequisites, V2 operational constraints, and secret-sanitization fixes included.

## Action needed
- **[security]** CSI request-log secret sanitization
  - CSI method-level request logs no longer bypass secret sanitization. The fix is included in v1.12.2.

## Check if affected
- **[breaking]** V2 Data Engine live-upgrade constraint
  - Applies if you perform a live upgrade of the V2 Data Engine from v1.12.2 to v1.13.0.
  - Live upgrade of the V2 Data Engine from v1.12.2 to v1.13.0 is not supported in this release.
- **[breaking]** Legacy linked-clone volume operation restriction
  - Applies if you upgrade to v1.12.1 or later.
  - After upgrading to v1.12.1 or later, `legacy linked-clone volumes` can only be detached or deleted. This restriction ships in v1.12.2.
- **[breaking]** V2 Data Engine CPU requirement
  - Applies if you configure fewer than 2 CPU cores for the V2 Data Engine.
  - The V2 Data Engine should be configured with at least 2 CPU cores for stability. With a multi-core mask, one core is reserved for the admin reactor, leaving one fewer core for I/O in v1.12.2.
- **[breaking]** `Kubernetes` v1.25 installation prerequisite
  - Applies if you install Longhorn v1.12.2 on a cluster running `Kubernetes` earlier than v1.25.
  - Longhorn v1.12.2 requires the cluster to run `Kubernetes` v1.25 or later before installation.

## Other recorded changes
- 74 (defect_corrected 60, value_changed 8, added 4, constraint_changed 2)

[Full analysis](https://ratatosk.io/en/releases/longhorn/v1.12.2)

[Original release notes](https://github.com/longhorn/longhorn/releases/tag/v1.12.2)