Skip to content

Releases: longhorn/longhorn

Longhorn v1.12.0

02 Jun 12:59
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.12.0 Release Notes

The Longhorn team is excited to announce the release of Longhorn v1.12.0. This feature release marks a major milestone for Longhorn: the V2 Data Engine is now officially Generally Available (GA).

With the V2 Data Engine reaching GA, Longhorn v1.12.0 strengthens the production story for modern workloads with topology-aware provisioning, dual-stack and V2 IPv6 support, improved observability and operational tooling, and clearer guidance around V1 and V2 behavior and feature parity.

For terminology and background on Longhorn releases, see Releases.

Removal

V2 Backing Image Removal

V2 Backing Images are removed in Longhorn v1.12.0. Suggest using the Containerized Data Importer (CDI) to import VM disk images into V2 volumes to achieve the same purpose.

If you have V2 volumes that were created from backing images, you must migrate them before upgrading to v1.12.0:

  1. Backup and recreate (recommended): Create a backup of the V2 volume, delete the original volume, then restore from backup. The restored volume will not have a backing image dependency.
  2. Delete the volume: If the data is not needed, delete the V2 volume directly.

V2 volumes with backing image dependencies cannot be upgraded in-place. Attempting to upgrade without migration may result in volume attachment failures.

GitHub Issue #13181

Primary Highlights

V2 Data Engine

Generally Available

We are pleased to announce that the V2 Data Engine has officially graduated to General Availability in Longhorn v1.12.0.

This milestone reflects major progress in stability, operational safety, networking support, and feature maturity. Compared with earlier releases, V2 volumes are better positioned for production use, combining GA readiness with modern networking support, more precise scheduling behavior, and clearer visibility into where V2 already matches V1 behavior and where differences still matter.

Important

V2 Live Upgrade:

V2 volumes do not support live upgrades between Longhorn v1.12 patch releases and must be detached before upgrading. Support is planned when upgrading from a Longhorn v1.12 release to a Longhorn v1.13 release.

V2 Volume Attach Latency at Scale:

In environments with a growing number of attached V2 volumes, increased attach latency has been observed for subsequent volumes. Initial analysis suggests this may be related to NVMe-TCP connection handling at scale, though the precise layer, SPDK user-space or Linux kernel, has not yet been identified. Further investigation is in progress. For follow-up status, see Issue #13241.

ARM64 NVMe-backed Block-Type Node Disk Limitation:

On ARM64 systems, V2 volumes may experience stuck I/O when SPDK is configured with two or more CPU cores and node disks use the NVMe driver. The root cause may lie in either the Linux kernel or SPDK itself, and further investigation is required. As a workaround, use AIO-backed node disks instead of NVMe-backed node disks on ARM64 systems. For follow-up status, see Issue #13243.

For a summary of the current V1 and V2 volume behavior differences and feature parity, see V1 and V2 Volume Feature Support.

Looking ahead, the roadmap remains active: fast volume cloning for V2 data engine (#12552) and Sharding Storage (Experimental Feature) (#1061) are planned for Longhorn v1.12.1.

Smarter Provisioning and Modern Networking

Topology-Aware PV Node Affinity Control

Longhorn v1.12.0 adds the csi-allowed-topology-keys setting and strictTopology StorageClass parameter for more precise control of PV nodeAffinity. These options allow users to limit which topology keys are propagated and, with WaitForFirstConsumer, pin the PV to the selected node topology when needed.

GitHub Issue #12684

IPv6 Support for V2 Volumes

V2 volumes now support single-stack IPv6 Kubernetes clusters.

GitHub Issue #10928

Dual-Stack Cluster Support

Longhorn now supports dual-stack Kubernetes clusters when all nodes are configured with their IP families in the same order, either all IPv4-first or all IPv6-first. This applies to both the V1 and V2 data engines.

Warning: Dual-stack clusters with mixed IP family ordering across nodes are not supported and may result in connectivity failures between replicas and the engine.

GitHub Issue #11531

Better Operations and Observability

Default CPU Allocation

Longhorn v1.12.0 changes the default data-engine-cpu-mask from 0x1, one CPU core, to 0x3, two CPU cores. V2 Data Engine uses a busy-polling reactor model where the master reactor handles both I/O polling and management RPCs. When only a single core is assigned, heavy I/O workloads can delay or starve RPC processing, resulting in increased latency, timeout events, and operational instability.

Assigning two or more cores allows I/O and management tasks to run on separate reactors, improving responsiveness and operational stability.

GitHub Issue #13237

On-Demand Snapshot Checksum Calculation

Longhorn v1.12.0 adds longhornctl support for triggering on-demand snapshot checksum calculation. The command can target a specific volume, all volumes on a specific node, or all volumes in the cluster, and the checksum operation runs asynchronously in the background.

GitHub Issue #11442

Toggle Kubernetes Metrics Server Integration

Longhorn v1.12.0 adds the Kubernetes Metrics Server Metrics Enabled setting to disable metrics-server-dependent metrics when the Kubernetes Metrics Server API is unavailable. This reduces repeated scrape warnings and unnecessary API calls while preserving other Longhorn metrics.

GitHub Issue #13011

Longhorn Manager Memory Optimization

Longhorn v1.12.0 optimizes longhorn-manager informer caching to reduce memory usage, especially in large clusters with high pod counts. This lowers cluster-wide memory overhead caused by repeated caching of non-Longhorn pod data on every manager instance.

GitHub Issue #12771

Configurable Engine Image Pod Liveness Probe

Longhorn v1.12.0 adds settings to configure the engine-image DaemonSet liveness probe period, timeout, and failure threshold. These settings help reduce unnecessary engine-image pod restarts on resource-constrained clusters, especially during upgrades or transient CPU spikes.

GitHub Issue #12846

Critical Stability Fixes

Instance Manager Stability During Replica Rebuild Storms

Longhorn v1.12.0 fixes an instance-manager panic that could occur during replica rebuild storms. In affected environments, the panic could terminate all iSCSI targets served by the instance-manager and trigger cascading volume detachments across multiple PVCs.

GitHub Issue #13087

Replica Rebuild Progress Reporting

Longhorn v1.12.0 fixes a replica rebuild progress reporting bug that could display values greater than 100% after file-sync retries on unstable networks. Progress accounting is now reset correctly for retried files, so rebuild progress remains within the valid 0% to 100% range.

GitHub Issue #12949

Replica Auto-Balance Scheduling Loop

Longhorn v1.12.0 fixes a regression in replica auto-balance that could trigger a repeated replica create-and-delete loop when Replica Auto Balance was set to best-effort. In affected clusters, Longhorn could keep scheduling an extra replica instead of stabilizing at the configured replica count.

GitHub Issue #12926

Replica CR Leak During Failed Local Scheduling

Longhorn v1.12.0 fixes a replica scheduling issue where large numbers of stopped Replica CRs could accumulate when dataLocality was set to best-effort and the node did not have enough eligible local disk space for another replica. In affected clusters, recurring reconciliation could keep creating placeholder Replica CRs instead of reusing a single failed-schedule placeholder.

GitHub Issue #13152

CSI Storage Capacity Tracking

Longhorn v1.12.0 fixes a CSIStorageCapacity scheduling issue that could cause compute nodes without Longhorn disks to report zero capacity and be rejected by WaitForFirstConsumer scheduling. In affected clusters with separated compute and storage nodes, new PVCs could remain pending even though eligible storage was available on storage nodes.

GitHub Issue #12807

Encrypted Volume Size Correction

Longhorn v1.12.0 pre-allocates the 16 MiB LUKS2 header in the replica backend file for encrypted volumes, so the dm-...

Read more

Longhorn v1.12.0-rc4

28 May 08:15
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.12.0-rc4 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Bug

Read more

Longhorn v1.12.0-rc3

22 May 08:26
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.12.0-rc3 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Bug

Read more

Longhorn v1.12.0-rc2

14 May 07:40
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.12.0-rc2 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Bug

Read more

Longhorn v1.12.0-rc1

11 May 06:25
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.12.0-rc1 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Bug

Read more

Longhorn v1.11.2

05 May 06:11
Immutable release. Only release title and notes can be modified.

Choose a tag to compare

Longhorn v1.11.2 Release Notes

Longhorn 1.11.2 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

Important Fixes

This release includes several critical stability fixes.

Replica rebuild progress fix

Resolved an issue where replica rebuild progress could exceed 100% under unstable network conditions. Progress reporting is now capped at 100%.

For more details, see #12949.

CSIStorageCapacity scheduling enhancement

Introduced a new setting to control CSIStorageCapacity reporting. Previously, compute nodes without Longhorn disks incorrectly reported 0 capacity, breaking WaitForFirstConsumer scheduling. With this enhancement, capacity tracking can be configured to avoid rejecting compute nodes in separated compute/storage architectures.

For more details, see #12807.

Improvement

Manager memory optimization

Optimized longhorn‑manager Pod informer caching to reduce cluster‑wide memory usage.

For more details, see #12771.

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.11.2.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.10.x or v1.11.0 to v1.11.2.

Important

Users on v1.11.0 who experienced the memory leaks of longhorn-instance-manager pods 12575 are highly encouraged to upgrade to v1.11.1 or later to receive the permanent fix for the proxy connection leaks.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues in this release

Improvement

  • [BACKPORT][v1.11.2][IMPROVEMENT] Reduce longhorn-manager memory usage by optimizing cluster-wide informer caching 12819 - @hookak @roger-ryao

Bug

  • [BACKPORT][v1.11.2][BUG] Test case test_storage_capacity_aware_pod_scheduling fails 13006 - @yangchiu @bachmanity1
  • [BACKPORT][v1.11.2][BUG] Replica Auto-Balance Causes Infinite Replica Scheduling Loop 12928 - @yangchiu @shuo-wu
  • [BACKPORT][v1.11.2][BUG] CSIStorageCapacity reports 0 for compute nodes without Longhorn disks, breaking WaitForFirstConsumer scheduling 12918 - @chriscchien @bachmanity1
  • [BACKPORT][v1.11.2][BUG] Replica rebuild progress can go over 100% 12952 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.2][BUG] Node exhaustion caused by backup inspect buildup induced due to NFS latency 12945 - @COLDTURNIP @roger-ryao
  • [BACKPORT][v1.11.2][BUG] Failed to collect health data for block disk (AIO) when disk path is a /dev/disk/by-id symlink 12911 - @yangchiu @hookak
  • [BACKPORT][v1.11.2][BUG] "snapshot becomes not ready to use" Warning events emitted during expected auto-cleanup after backup 12856 - @EpochBoy @yangchiu

Stability

Contributors

Longhorn v1.11.1

13 Mar 00:42

Choose a tag to compare

Longhorn v1.11.1 Release Notes

Longhorn v1.11.1 is a patch release that focuses on critical bug fixes, security hardening, and stability improvements for both V1 and V2 data engines. Key highlights include a fix for a significant memory leak in the instance manager and improvements to backup reliability and volume scheduling.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

Important Fixes

This release includes several critical stability fixes.

Longhorn workload pods memory leak

Fixed a critical regression where proxy connection leaks in the longhorn-instance-manager pods caused high memory consumption.

For more details, see #12575

Backup & Restore compatibility fix

Resolved compatibility issues introduced by aws-go-sdk v2, including backups to S3-compatible storage (like Storj or Google Cloud Storage). This fix ensures the completion of large data transfers to remote backup targets with correct authorization.

For more details, see #12714 and 12688

V2 Data Engine (SPDK) refinements

Several enhancements were delivered for some V2 Data Engine features, including fast replica rebuild and clone.

For more details, see #12751 and 12748

CSI scheduling enhancement

Support CSI topology-aware PV nodeAffinity control.

For more details, see #12689 and 12656

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.11.1.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.10.x or v1.11.0 to v1.11.1.

Important

Users on v1.11.0 who experienced the memory leaks of longhorn-instance-manager pods 12575 are highly encouraged to upgrade to v1.11.1 to receive the permanent fix for the proxy connection leaks.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues in this release

Improvement

  • [BACKPORT][v1.11.1][IMPROVEMENT] Ensure V2 Engine ReplicaAdd respects the fast-replica-rebuild-enabled setting 12751 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] Topology-aware PV nodeAffinity control: allowedTopologies keys + strictTopology 12689 - @hookak @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] detailed log for the reason of node controller deleting backing image copies 12585 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.11.1][IMPROVEMENT] Relax endpoint-network-for-rwx-volume validation for migratable block-mode volumes 12711 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][IMPROVEMENT] RBAC permissions for csi-resizer 12694 - @yangchiu

Bug

  • [BACKPORT][v1.11.1][BUG] Failed replicas accumulate during engine upgrade 12768 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] V2 Volume Clone Status is Changed Over Time 12748 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backup to S3 fails at 95% 12714 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] spdk_tgt encountered an assertion failure in longhorn-spdk-helper during a CI test run 12738 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Google Cloud Storage (GCS) backup target always fails with SignatureDoesNotMatch due to AWS SDK Go v2 CRC32 checksum incompatibility 12688 - @mantissahz @chriscchien
  • [BACKPORT][v1.11.1][BUG] Enable to set defaultSettings.nodeDiskHealthMonitoring 12730 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] stale name variable in nsmounter get_pid 12704 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] After upgrading to 1.11.0, new persistent volumes have nodeAffinity 12665 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] Incorrect storage double-counting causes scheduling failure when multiple replicas exist on the same node 12661 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Recreated block disk with same name never becomes schedulable after volume and disk deletion 12641 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Longhorn v1.10 Volume API is not compatible with the v1.8.1 manifest 12618 - @mantissahz @roger-ryao
  • [BACKPORT][v1.11.1][BUG] [v2] Can't use partition as block device 12626 - @bachmanity1
  • [BACKPORT][v1.11.1][BUG] Volume.Spec.CloneMode is empty after upgrading to v1.10.x and following version 12615 - @mantissahz
  • [BACKPORT][v1.11.1][BUG] Longhorn validating webhook blocks k3s server node joins - flannel CNI fails to initialize 12589 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] V1.11.0 very high memory consumption for instance manager 12575 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backing image data source pod fails when HTTP proxy is enabled 12780 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node 12788 - @COLDTURNIP @roger-ryao

Stability

Contributors

Longhorn v1.11.0

29 Jan 06:00

Choose a tag to compare

Longhorn v1.11.0 Release Notes

The Longhorn team is excited to announce the release of Longhorn v1.11.0. This release marks a major milestone, with the V2 Data Engine officially entering the Technical Preview stage following significant stability improvements.

Additionally, this version optimizes the stability of the whole system and introduces critical improvements in resource observability, scheduling, and utilization.

For terminology and background on Longhorn releases, see Releases.

Warning

Hotfix

longhorn-instance-manager Image

The longhorn-instance-manager:v1.11.0 image is affected by a regression issue introduced by the new longhorn-instance-manager Proxy service APIs. The bug causes Proxy connection leaks in the longhorn-instance-manager pods, resulting in increased memory usage. To mitigate this issue, replace longhornio/longhorn-instance-manager:v1.11.0 with the hotfixed image longhornio/longhorn-instance-manager:v1.11.0-hotfix-1.

You can apply the update by following these steps:

  1. Update the longhorn-instance-manager image

    • Change the longhorn-instance-manager image tag from v1.11.0 to v1.11.0-hotfix-1 in the appropriate file:
      • For Helm: Update values.yaml
      • For manifests: Update the deployment manifest directly.
  2. Proceed with the installation or upgrade

    • Apply the changes using your standard Helm install/upgrade command or reapply the updated manifest.

longhorn-manager Image

The longhorn-manager:v1.11.0 image is affected by a regression issue introduced by the new Kubernetes Node validator. The bug blocks setting Kubernetes node CNI labels because it waits for the Longhorn webhook server to be running, while the Longhorn webhook server waits for CNI network to be ready. To mitigate this issue, replace longhornio/longhorn-manager:v1.11.0 with the hotfixed image longhornio/longhorn-manager:v1.11.0-hotfix-1.

You can apply the update by following these steps:

  1. Disable the upgrade version check
  • Helm users: Set upgradeVersionCheck to false in the values.yaml file.
  • Manifest users: Remove the --upgrade-version-check flag from the deployment manifest.
  1. Update the longhorn-manager image
  • Change the longhorn-manager image tag from v1.11.0 to v1.11.0-hotfix-1 in the appropriate file:
    • For Helm: Update values.yaml.
    • For manifests: Update the deployment manifest directly.
  1. Proceed with the installation or upgrade
  • Apply the changes using your standard Helm install/upgrade command or reapply the updated manifest.

Deprecation

V2 Backing Image Deprecation

The Backing Image feature for the V2 Data Engine is now deprecated in v1.11.0 and is scheduled for removal in v1.12.0.

Users using V2 volumes for virtual machines are encouraged to adopt the Containerized Data Importer (CDI) for volume population instead.

GitHub Issue #12237

Primary Highlights

V2 Data Engine

Now in Technical Preview Stage

We are pleased to announce that the V2 Data Engine has officially graduated to the Technical Preview stage. This indicates increased stability and feature maturity as we move toward General Availability.

Limitation: While the engine is in Technical Preview, live upgrade is not supported yet. V2 volumes must be detached (offline) before engine upgrade.

Support for ublk Frontend

Longhorn supports configuring UBLK performance parameters globally, per volume, or via StorageClass to improve I/O performance.

GitHub Issue #11039

V1 Data Engine

Faster Replica Rebuilding from Multiple Sources

The V1 Data Engine now supports parallel rebuilding. When a replica needs to be rebuilt, the engine can now stream data from multiple healthy replicas simultaneously rather than a single source. This significantly reduces the time required to restore redundancy for volumes containing tons of scattered data chunks.

GitHub Issue #11331

General

Balance-Aware Algorithm Disk Selection For Replica Scheduling

Longhorn improves the disk selection for the replica scheduling by introducing an intelligent balance-aware scheduling algorithm, reducing uneven storage usage across nodes and disks.

GitHub Issue #10512

Node Disk Health Monitoring

Longhorn now actively monitors the physical health of the underlying disks used for storage by using S.M.A.R.T. data. This allows administrators to identify issues and raise alerts when abnormal SMART metrics are detected, helping prevent failed volumes.

GitHub Issue #12016

Share Manager Networking

Users can now configure an extra network interface for the Share Manager to support complex network segmentation requirements.

GitHub Issue #10269

ReadWriteOncePod (RWOP) Support

Full support for the Kubernetes ReadWriteOncePod access mode has been added.

GitHub Issue #9727

StorageClass allowedTopologies Support

Administrators can now use the allowedTopologies field in Longhorn StorageClasses to restrict volume provisioning to specific zones, regions, or nodes within the cluster.

GitHub Issue #12261

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.11.0.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.10.x to v1.11.0.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues in this release

Highlight

Feature

Impro...

Read more

Longhorn v1.10.2

28 Jan 09:24

Choose a tag to compare

Longhorn v1.10.2 Release Notes

Longhorn 1.10.2 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

Warning

HotFix

The backing-image-manager:v1.10.2 image is affected by

To mitigate the issues, replace backing-image-manager:v1.10.2 with the hotfixed image backing-image-manager:v1.10.2-hotfix-1.

Follow these steps to apply the update:

  1. Update the backing-image-manager image

    • Change the image tag from v1.10.2 to v1.10.2-hotfix-1 in the appropriate file:
      • For Helm: Update values.yaml
      • For manifests: Update the deployment manifest directly.
  2. Proceed with the upgrade

  • Apply the changes using your standard Helm upgrade command or reapply the updated manifest.

Important Fixes

This release includes several critical stability fixes.

RWX Volume Unavailable After Node Drain

Fixed a race condition where ReadWriteMany (RWX) volumes could remain in the attaching state after node drains, causing workloads to become unavailable.

For more details, see Issue #12231.

Encrypted Volume Cannot Be Expanded Online

Fixed an issue where online expansion of encrypted volumes did not propagate the new size to the dm-crypt device.

For more details, see Issue #12368.

Cloned Volume Cannot Be Attached to Workload

Fixed a bug where cloned volumes could fail to reach a healthy state, preventing attachment to workloads.

For more details, see Issue #12208.

Block Mode Volume Migration Stuck

Fixed a regression in block-mode volume migrations where newly created replicas could incorrectly inherit the lastFailedAt timestamp from source replicas, causing repeated deletion and blocking migration completion.

For more details, see Issue #12312.

Replica Auto Balance Disk Pressure Threshold Stalled

Fixed an issue where replica auto-balance under disk pressure could be blocked if stopped volumes were present on the disk.

For more details, see Issue #12334.

Replicas Accumulate During Engine Upgrade

Fixed a bug where temporary replicas could accumulate during engine upgrade. High etcd latency could cause new replicas to fail verification, leading to accumulation over multiple reconciliation cycles.

For more details, see Issue #12115.

Potential Client Connection and Context Leak

Fixed potential context leaks in the instance manager client and backing image manager client, improving stability and preventing resource exhaustion.

For more details, see Issue #12200 and Issue #12195.

Replica Node Level Soft Anti-Affinity Ignored

Fixed a bug of replica scheduling loop where replicas could be scheduled onto nodes that already host a replica, even when Replica Node-Level Soft Anti-Affinity was disabled.

For more details, see Issue #12251.

Installation

Important

Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.10.2.

You can install Longhorn using a variety of tools, including Rancher, Kubectl, and Helm. For more information about installation methods and requirements, see Quick Installation in the Longhorn documentation.

Upgrade

Important

Ensure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.9.x to v1.10.2.

Longhorn only allows upgrades from supported versions. For more information about upgrade paths and procedures, see Upgrade in the Longhorn documentation.

Post-Release Known Issues

For information about issues identified after this release, see Release-Known-Issues.

Resolved Issues

Feature

  • [BACKPORT][v1.10.2][FEATURE] Inherit namespace for longhorn-share-manager in FastFailover mode 12245 - @yangchiu
  • [BACKPORT][v1.10.2][FEATURE] [Dependency] aws-sdk-go v1.55.7 is EOL as of 2025-07-31 — plan to migrate to v2? 12181 - @mantissahz @roger-ryao

Improvement

  • [BACKPORT][v1.10.2][IMPROVEMENT] Fix V2 Volume CSI Clone Slowness Caused by VolumeAttachment Webhook Blocking 12329 - @PhanLe1010 @roger-ryao

Bug

Contributors

Read more

Longhorn v1.11.0-rc3

22 Jan 08:51

Choose a tag to compare

Longhorn v1.11.0-rc3 Pre-release
Pre-release

DON'T UPGRADE from/to any RC/Preview/Sprint releases because the operation is not supported.

Resolved Issues in this release

Highlight

Feature

Improvement

Read more