Update Helm release longhorn to v1.9.0

Update Helm release longhorn to v1.9.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.8.1 -> 1.9.0

Release Notes

longhorn/longhorn (longhorn)

v1.9.0: Longhorn v1.9.0

Compare Source

Longhorn v1.9.0 Release Notes

Longhorn v1.9.0 introduces new features, enhancements, and bug fixes aimed at improving system stability and user experience. Key highlights include V2 Data Engine improvements, orphaned instance deletion, offline replica rebuilding, recurring system backups, and enhanced observability of Longhorn resources.

The Longhorn team appreciates your contributions and anticipates receiving feedback regarding this release.

For terminology and background on Longhorn releases, see Releases.

Removal

Environment Check Script

The environment_check.sh script, deprecated in v1.7.0, has been removed in v1.9.0. Use the Longhorn Command Line Tool (longhornctl) to check your environment for potential issues.

Orphan Resource Auto-Deletion

The orphan-auto-deletion setting has been replaced by orphan-resource-auto-deletion in v1.9.0. To replicate the previous behavior, include replica-data in the orphan-resource-auto-deletion value. During the upgrade, the original orphan-auto-deletion setting is automatically migrated.

For more information, see Orphan Data Cleanup.

Deprecated Fields in longhorn.io/v1beta2 CRDs

Deprecated fields have been removed from the CRDs. For details, see issue #​6684.

Deprecation & Incompatibilities

longhorn.io/v1beta1 API

The v1beta1 version of the Longhorn API is marked unserved and unsupported in v1.9.0 and will be removed in v1.10.0.

For more details, see Issue #​10250.

Breaking Change in V2 Backing Image

Starting with Longhorn v1.9.0, V2 backing images are incompatible with earlier versions due to naming conflicts in the extended attributes (xattrs) used by SPDK backing image logical volumes. As a result, V2 backing images must be deleted and recreated during the upgrade process. Since backing images cannot be deleted while volumes using them still exist, you must first back up, delete, and later restore those volumes as the following steps:

  • Before upgrading to v1.9.0:
    • Verify that backup targets are functioning properly.
    • Create full backups of all volumes that use a V2 backing image.
    • Detach and delete these volumes after the backups complete.
    • In the Backing Image page, save the specifications of all V2 backing images, including the name and the image source.
    • Delete all V2 backing images.
  • After upgrading:
    • Recreate the V2 backing images using the same names and image sources.
    • Restore the volumes from your backups.

For more details, see Issue #​10805.

Primary Highlights

New V2 Data Engine Features

While the V2 Data Engine remains experimental in this release, several core functions have been significantly improved:

  • Support UBLK Frontend: Support for UBLK frontend in the V2 Data Engine, which allows for better performance and resource utilization.
  • Storage Network: Introduces support for storage networks in the V2 Data Engine to allow network segregation.
  • Offline Replica Rebuilding: Support for offline replica rebuilding, which allows degraded volumes to automatically recover replicas even while the volume is detached. This capability ensures high data availability without manual intervention.
Recurring System Backup

Starting with Longhorn v1.9.0, you can create a recurring job for system backup creation.

Documentation | GitHub Issue

Offline Replica Rebuilding

Longhorn introduces offline replica rebuilding, a feature that allows degraded volumes to automatically recover replicas even while the volume is detached. This capability minimizes the need for manual recovery steps, accelerates restoration, and ensures high data availability. By default, offline replica rebuilding is disabled. To enable it, set the offline-replica-rebuilding setting to true in the Longhorn UI or CLI.

Documentation | GitHub Issue

Orphaned Instance Deletion

Longhorn can now track and remove orphaned instances, which are leftover resources like replicas or engines that are no longer associated with an active volume. These instances may accumulate due to unexpected failures or incomplete cleanup.

To reduce resource usage and maintain system performance, Longhorn supports both automatic and manual cleanup. By default, this feature is disabled. To enable it, set the orphan-resource-auto-deletion setting to instance in the Longhorn UI or CLI.

Documentation | GitHub Issue

Improved Metrics for Replica, Engine, and Rebuild Status

Longhorn improves observability with new Prometheus metrics that expose the status and identity of Replica and Engine CRs, along with rebuild activity. These metrics make it easier to monitor rebuilds across the cluster.

For more information, see #​10550 and #​10722.

Installation

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

New Contributors

Contributors

Read more

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