This page summarizes the key notes for Longhorn v1.11.0. For the full release note, see here.

• Deprecation
• Behavior Change
  • Cloned Volume Health After Efficient Cloning
• General
  • Kubernetes Version Requirement
  • Upgrade Check Events
  • Manual Checks Before Upgrade
• Scheduling
  • Replica Scheduling with Balance Algorithm
• Monitoring
  • Disk Health Monitoring
• V2 Data Engine
  • Longhorn System Upgrade

Deprecation

V2 Backing Image is deprecated and will be removed in a future release. Users can used containerized data importer (CDI) to import images into Longhorn as an alternative. For more information, see Longhorn with CDI Imports.

Behavior Change

Cloned Volume Health After Efficient Cloning

With efficient cloning enabled, a newly cloned and detached volume is degraded and has only one replica, with its clone status set to copy-completed-awaiting-healthy. To bring the volume to a healthy state, transition the clone status to completed and rebuild the remaining replica by either enabling offline replica rebuilding or attaching the volume to trigger replica rebuilding. See Issue #12341 and Issue #12328.

General

Kubernetes Version Requirement

Due to the upgrade of the CSI external snapshotter to v8.2.0, all clusters must be running Kubernetes v1.25 or later before you can upgrade to Longhorn v1.8.0 or a newer version.

Upgrade Check Events

When upgrading via Helm or Rancher App Marketplace, Longhorn performs pre-upgrade checks. If a check fails, the upgrade stops, and the reason for the failure is recorded in an event.

For more detail, see Upgrading Longhorn Manager.

Manual Checks Before Upgrade

Automated pre-upgrade checks do not cover all scenarios. Manual checks via kubectl or the UI are recommended:

• Ensure all V2 Data Engine volumes are detached and replicas are stopped. The V2 engine does not support live upgrades.
• Avoid upgrading when volumes are “Faulted”, as unusable replicas may be deleted, causing permanent data loss if no backups exist.
• Avoid upgrading if a failed BackingImage exists. See Backing Image for details.
• Creating a Longhorn system backup before upgrading is recommended to ensure recoverability.

Scheduling

Replica Scheduling with Balance Algorithm

To improve data distribution and resource utilization, Longhorn introduces a balance algorithm that schedules replicas evenly across nodes and disks based on calculated balance scores.

For more information, see Scheduling.

Monitoring

Disk Health Monitoring

Starting with Longhorn v1.11.0, disk health monitoring is available for both V1 and V2 data engines. Longhorn collects health data from disks and exposes it through Prometheus metrics and Longhorn Node Custom Resources.

Key Features:

• Automatic health data collection every 10 minutes
• Disk health status and detailed attributes exposed as Prometheus metrics
• Health data available in nodes.longhorn.io Custom Resources

Note:

• SMART data may not be fully available in virtualized or cloud environments (e.g., AWS EBS), which may result in zero values for certain attributes.
• Available health attributes vary depending on disk type and hardware.

For more information, see Disk Health Monitoring.

V2 Data Engine

Longhorn System Upgrade

Live upgrades of V2 volumes are not supported. Ensure all V2 volumes are detached before upgrading.