longhorn

Update Helm release longhorn to v1.10.0

Michi Kofler-Häusler

Michi Kofler-Häusler

— 16 min read
Update Helm release longhorn to v1.10.0
Photo by Tony Garcia / Unsplash

No problems deploying to Proxmox VE K3s Kubernetes cluster via Helm Chart and Flux V2 reconciliation in a GitOps approach.

This MR contains the following updates:

Package Update Change
longhorn (source) minor 1.9.1 -> 1.10.0

Release Notes

longhorn/longhorn (longhorn)

v1.10.0: Longhorn v1.10.0

Compare Source

Longhorn v1.10.0 Release Notes

Longhorn v1.10.0 is a major release focused on improving stability, performance, and the overall user experience. This version introduces significant enhancements to our core features, including the V2 Data Engine, and streamlines configuration for easier management.

The key highlights include improvements to the V2 Data Engine, enhanced resilience, simplified configuration, and better observability.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

Removal

longhorn.io/v1beta1 API

The v1beta1 Longhorn API version has been removed.

See GitHub Issue #​10249 for details.

replica.status.evictionRequested Field

The deprecated replica.status.evictionRequested field has been removed.

See GitHub Issue #​7022 for details.

Primary Highlights

New V2 Data Engine Features
Interrupt Mode Support

Interrupt mode has been added to the V2 Data Engine to help reduce CPU usage. This feature is especially beneficial for clusters with idle or low I/O workloads, where conserving CPU resources is more important than minimizing latency.

While interrupt mode lowers CPU consumption, it may introduce slightly higher I/O latency compared to polling mode. In addition, the current implementation uses a hybrid approach, which still incurs a minimal, constant CPU load even when interrupts are enabled.

[!NOTE]
Limitation: Supports AIO disks only.

See Interrupt Mode and GitHub Issue#9834 for details.

Volume and Snapshot Cloning

V2 volumes now support two types of cloning:

  • Full-Copy Clone: Creates a new PVC with a complete, independent copy of the source data, providing full isolation.
  • Linked-Clone (Fast/Smart Clone): Creates a PVC that shares data blocks with the source volume for near-instant creation. Ideal for temporary workloads, backups, or testing. Linked-clones are lightweight, fast, and reduce storage overhead.

See Volume Clone Support and GitHub Issue#7794 for details.

Replica Rebuild QoS

Provides Quality of Service (QoS) control for V2 volume replica rebuilds. You can configure bandwidth limits globally or per volume to prevent storage throughput overload on source and destination nodes.

See Replica Rebuild QoS and GitHub Issue#10770 for details.

Volume Expansion

Longhorn now supports volume expansion for V2 Data Engine volumes. You can expand the volume through the UI or by modifying the PVC manifest.

See V2 Volume Expansion and GitHub Issue#8022 for details.

Support for Running Without Hugepages

This reduces memory pressure on low-spec nodes and increases deployment flexibility. Performance may be lower compared to running with Hugepages.

See GitHub Issue#7066 for details.

New V1 Data Engine Features
IPv6 Support

V1 volumes now support single-stack IPv6 Kubernetes clusters.

Warning: Dual-stack Kubernetes clusters and V2 volumes are not supported in this release.

See GitHub Issue #​2259 for details.

Consolidated Global Settings

To simplify management, Longhorn settings are now unified across V1 and V2 Data Engines, using a new, more flexible JSON format.

  • Single value (applies to all Data Engines): Non-JSON string (e.g., 1024).
  • Data-engine-specific: JSON object (e.g., {"v1": "value1", "v2": "value2"})
  • V1-only: JSON object with v1 key (e.g., {"v1":"value1"}).
  • V2-only: JSON object with v2 key (e.g., {"v2":"value1"}).

See Longhorn Settings and GitHub Issue#10926 for details.

Pod Scheduling with CSIStorageCapacity

Longhorn now supports CSIStorageCapacity, allowing Kubernetes to verify node storage before scheduling pods using StorageClasses with WaitForFirstConsumer. This reduces scheduling errors and improves reliability.

See GitHub Issue #​10685 for details.

Configurable Backup Block Size

Backup block size can now be configured when creating a volume to optimize performance and efficiency.

See Create Longhorn Volumes and GitHub Issue#5215 for details.

Volume Attachment Summary

The UI now shows a summary of attachment tickets on each volume page for improved visibility.

See GitHub Issue #​11400 for details.

Installation

[!IMPORTANT]
Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.10.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.9.x to v1.10.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.

Highlight
Feature
Improvement
Bug
Stability
Misc

New Contributors

Contributors

v1.9.2: Longhorn v1.9.2

Compare Source

Longhorn v1.9.2 Release Notes

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

The Longhorn team appreciates your contributions and expects to receive feedback regarding this release.

[!NOTE]
For more information about release-related terminology, see Releases.

Installation

[!IMPORTANT]
Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.9.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.8.x or v1.9.x (< v1.9.2) to v1.9.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

Improvement
Bug

New Contributors

Contributors

Read more

Me on Mastodon - This link is here for verification purposes.