Skip to content

Releases: longhorn/longhorn

Longhorn v1.8.0

22 Jan 07:50
Compare
Choose a tag to compare

Longhorn v1.8.0 Release Notes

This latest version of Longhorn introduces several features, enhancements, and bug fixes that are intended to improve system quality and the overall user experience. Highlights include new V2 Data Engine features, multiple backupstores, automatic RWX volume expansion, installation and upgrades via Helm Controller, and V2 Data Engine Support for Talos Linux.

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

For more information about release-related terminology, see Releases.

Important

The CSI external-snapshotter was upgraded to v8.2.0. Ensure that all clusters are running Kubernetes v1.25 or later before upgrading to Longhorn v1.8.0 or a later version.

Deprecation & Incompatibilities

  • The default block size for block-type disks in earlier Longhorn releases is 4096 bytes. However, 512 bytes is more commonly used and aligns with the V1 Data Engine's configuration. Additionally, the 4096-byte block size is incompatible with backing images generated by the V1 Data Engine. To address these concerns, the default block size was changed to 512 bytes.

    If you have existing V2 volumes, perform the following steps:

    1. Back up the V2 volumes.
    2. Remove the V2 volumes.
    3. Delete the block-type disk with a 4096-byte block size from node.spec.disks.
    4. Erase the old data on the block-type disk using tools such as dd.
    5. Add the disk again to node.spec.disks with the updated configuration.
    6. Restore the V2 volumes.

    For more information, see #10053.

  • A V2 volume data corruption issue that affects earlier Longhorn releases has been resolved in v1.8.0. The issue involves potential continual changes to the checksum of files in a V2 volume with multiple replicas. This occurs because SPDK allocates clusters without initialization, leading to data inconsistencies across replicas. The varying data read from the volume can result in data corruption and broken backups. For more information, see #10035.

Primary Highlights

New V2 Data Engine Features

Although the V2 Data Engine is still considered an experimental feature in this release, the core functions have been significantly enhanced.

Multiple Backupstores and Default Backup Target

Starting with v1.8.0, Longhorn allows you to use multiple backupstores for storing backups of Longhorn volumes. Longhorn v1.8.0 also creates a default backup target (default) during installation and upgrades. The default backup target is used for system backups and volumes that were created without an assigned backup target name.

Demo | Documentation | GitHub Issue

Automatic RWX Volume Expansion

Longhorn v1.8.0 supports fully automatic online expansion of RWX volumes without the need to scale down the workload or apply manual commands. To use this feature, ensure that the v1.8.0 versions of Longhorn Manager, Share Manager, and the CSI plugin are all running.

Documentation | GitHub Issue

Helm Controller

You can now install and upgrade Longhorn on clusters running RKE2 or K3s using the Helm Controller that is built into those distributions. The Helm Controller manages Helm charts using a HelmChart Custom Resource Definition (CRD), which contains most of the options that would normally be passed to the Helm command-line tool.

Documentation | GitHub Issue

V2 Data Engine Support for Talos Linux

Longhorn v1.8.0 supports usage of V2 volumes in Talos Linux clusters. To use this feature, ensure that all nodes meet the V2 Data Engine prerequisites.

Documentation | GitHub Issue

Installation

Important

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

  • [IMPROVEMENT] ...
Read more

Longhorn v1.8.0-rc5

20 Jan 08:41
Compare
Choose a tag to compare
Longhorn v1.8.0-rc5 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

Longhorn v1.8.0-rc4

17 Jan 03:19
Compare
Choose a tag to compare
Longhorn v1.8.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

Read more

Longhorn v1.8.0-rc3

13 Jan 08:26
Compare
Choose a tag to compare
Longhorn v1.8.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

Longhorn v1.6.4

03 Jan 05:11
Compare
Choose a tag to compare

Longhorn v1.6.4 Release Notes

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

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.21 or later before installing Longhorn v1.6.4.

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.21 or later before upgrading from Longhorn v1.5.x or v1.6.x (< v1.6.4) to v1.6.4.

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

Deprecation & Incompatibilities

For information about important changes, including feature incompatibility, deprecation, and removal, see Important Notes in the Longhorn documentation.

Post-Release Known Issues

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

Resolved Issues

Improvement

Bug

  • [BUG][v1.6.x-head] Share manager pod kept restarting 10096 - @c3y1huang @chriscchien
  • [BACKPORT][v1.6.4][BUG] Webhook servers initialization blocks longhorn-manager from running 10067 - @c3y1huang
  • [BACKPORT][v1.6.4][BUG] Missing fromBackup Parameter in API Request When Restoring Multiple Files from Backup List 10065 - @a110605 @chriscchien
  • [BACKPORT][v1.6.4][BUG] Busrt ISCSI Connection Errors, and IM Pod Restarting to make LH Volume disconnection 9890 - @yangchiu @ChanYiLin @chriscchien
  • [BACKPORT][v1.6.4][BUG] Failed to inspect the backup backing image information if NFS backup target URL with options 9704 - @yangchiu @mantissahz @chriscchien
  • [BACKPORT][v1.6.4][BUG] Error notification appears on the volume backup details page 10070 - @a110605 @houhoucoop
  • [BACKPORT][v1.6.4][BUG][v1.8.x] Unable to add block disk after node deleted and added back 10041 -
  • [BACKPORT][v1.6.4][BUG] Detached Volume Stuck in Attached State During Node Eviction 9809 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Backup progress should not add block failed to upload to successful count 9792 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] S3 Backup target reverts randomly to previous value 9589 - @c3y1huang
  • [BACKPORT][v1.6.4][BUG] Old backups are not cleaned up after timeout 9730 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] Share manager is permanently stuck in stopping/error if we shutdown the node of share manager pod. This makes RWX PVC cannot attach to any new node 9855 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.6.4][BUG] Test case test_node_eviction_multiple_volume failed to reschedule replicas after volume detached 9867 - @yangchiu @c3y1huang
  • [BACKPORT][v1.6.4][BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore 9802 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Fail to resize RWX PVC at filesystem resizing step 9737 - @james-munson
  • [BACKPORT][v1.6.4][BUG] Test case Stopped replicas on deleted nodes should not be counted as healthy replicas when draining nodes fails 9625 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] Pre-upgrade pod should event the reason for any failures. 9644 - @yangchiu @james-munson
  • [BACKPORT][v1.6.4][BUG] All Backups are lost in the Backup Target if the NFS Service Disconnects and Reconnects again 9543 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] kubectl drain node is blocked by unexpected orphan engine processes 9443 - @ejweber

Misc

Contributors

Longhorn v1.6.4-rc2

02 Jan 09:16
Compare
Choose a tag to compare
Longhorn v1.6.4-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

Improvement

Bug

  • [BUG][v1.6.x-head] Share manager pod kept restarting 10096 - @c3y1huang @chriscchien
  • [BACKPORT][v1.6.4][BUG] Webhook servers initialization blocks longhorn-manager from running 10067 - @c3y1huang
  • [BACKPORT][v1.6.4][BUG] Missing fromBackup Parameter in API Request When Restoring Multiple Files from Backup List 10065 - @a110605 @chriscchien
  • [BACKPORT][v1.6.4][BUG] Busrt ISCSI Connection Errors, and IM Pod Restarting to make LH Volume disconnection 9890 - @yangchiu @ChanYiLin @chriscchien
  • [BACKPORT][v1.6.4][BUG] Failed to inspect the backup backing image information if NFS backup target URL with options 9704 - @yangchiu @mantissahz @chriscchien
  • [BACKPORT][v1.6.4][BUG] Error notification appears on the volume backup details page 10070 - @a110605 @houhoucoop
  • [BACKPORT][v1.6.4][BUG][v1.8.x] Unable to add block disk after node deleted and added back 10041 -
  • [BACKPORT][v1.6.4][BUG] Detached Volume Stuck in Attached State During Node Eviction 9809 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Backup progress should not add block failed to upload to successful count 9792 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] S3 Backup target reverts randomly to previous value 9589 - @c3y1huang
  • [BACKPORT][v1.6.4][BUG] Old backups are not cleaned up after timeout 9730 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] Share manager is permanently stuck in stopping/error if we shutdown the node of share manager pod. This makes RWX PVC cannot attach to any new node 9855 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.6.4][BUG] Test case test_node_eviction_multiple_volume failed to reschedule replicas after volume detached 9867 - @yangchiu @c3y1huang
  • [BACKPORT][v1.6.4][BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore 9802 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Fail to resize RWX PVC at filesystem resizing step 9737 - @james-munson
  • [BACKPORT][v1.6.4][BUG] Test case Stopped replicas on deleted nodes should not be counted as healthy replicas when draining nodes fails 9625 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] Pre-upgrade pod should event the reason for any failures. 9644 - @yangchiu @james-munson
  • [BACKPORT][v1.6.4][BUG] All Backups are lost in the Backup Target if the NFS Service Disconnects and Reconnects again 9543 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] kubectl drain node is blocked by unexpected orphan engine processes 9443 - @ejweber

Misc

Contributors

Longhorn v1.8.0-rc2

02 Jan 09:19
Compare
Choose a tag to compare
Longhorn v1.8.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

Read more

Longhorn v1.6.4-rc1

24 Dec 07:12
Compare
Choose a tag to compare
Longhorn v1.6.4-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

Improvement

Bug

  • [BACKPORT][v1.6.4][BUG][v1.8.x] Unable to add block disk after node deleted and added back 10041 -
  • [BACKPORT][v1.6.4][BUG] Detached Volume Stuck in Attached State During Node Eviction 9809 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Backup progress should not add block failed to upload to successful count 9792 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] Busrt ISCSI Connection Errors, and IM Pod Restarting to make LH Volume disconnection 9890 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.6.4][BUG] S3 Backup target reverts randomly to previous value 9589 - @c3y1huang
  • [BACKPORT][v1.6.4][BUG] Old backups are not cleaned up after timeout 9730 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] Share manager is permanently stuck in stopping/error if we shutdown the node of share manager pod. This makes RWX PVC cannot attach to any new node 9855 - @yangchiu @PhanLe1010
  • [BACKPORT][v1.6.4][BUG] Test case test_node_eviction_multiple_volume failed to reschedule replicas after volume detached 9867 - @yangchiu @c3y1huang
  • [BACKPORT][v1.6.4][BUG] DR volume fails to reattach and faulted after node stop and start during incremental restore 9802 - @c3y1huang @roger-ryao
  • [BACKPORT][v1.6.4][BUG] Fail to resize RWX PVC at filesystem resizing step 9737 - @james-munson
  • [BACKPORT][v1.6.4][BUG] Test case Stopped replicas on deleted nodes should not be counted as healthy replicas when draining nodes fails 9625 - @yangchiu @derekbit
  • [BACKPORT][v1.6.4][BUG] Failed to inspect the backup backing image information if NFS backup target URL with options 9704 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] Pre-upgrade pod should event the reason for any failures. 9644 - @yangchiu @james-munson
  • [BACKPORT][v1.6.4][BUG] All Backups are lost in the Backup Target if the NFS Service Disconnects and Reconnects again 9543 - @yangchiu @mantissahz
  • [BACKPORT][v1.6.4][BUG] kubectl drain node is blocked by unexpected orphan engine processes 9443 - @ejweber

Misc

Contributors

Longhorn v1.8.0-rc1

19 Dec 09:06
Compare
Choose a tag to compare
Longhorn v1.8.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

Read more

Longhorn v1.7.2

18 Oct 06:12
Compare
Choose a tag to compare

Longhorn v1.7.2 Release Notes

Longhorn 1.7.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.21 or later before installing Longhorn v1.7.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.21 or later before upgrading from Longhorn v1.6.x or v1.7.x (< v1.7.0) to v1.7.2.

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

Deprecation & Incompatibilities

The functionality of the environment check script overlaps with that of the Longhorn CLI, which is available starting with v1.7.0. Because of this, the script is deprecated in v1.7.0 and is scheduled for removal in v1.8.0.

For information about important changes, including feature incompatibility, deprecation, and removal, see Important Notes in the Longhorn documentation.

Post-Release Known Issues

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

Resolved Issues

Improvement

Bug

  • [BACKPORT][v1.7.2][BUG] longhornctl install preflight --operating-system=cos failed on COS_CONTAINERD 9666 - @c3y1huang @chriscchien
  • [BACKPORT][v1.7.2][BUG] System Restore Stuck at Pending due to Tolerations not Applied 9655 - @c3y1huang @chriscchien
  • [BACKPORT][v1.7.2][BUG][v1.7.x] Disks modal broken layout 9633 - @a110605 @roger-ryao
  • [BACKPORT][v1.7.2][BUG] Single Replica Node Down test cases fail 9628 - @yangchiu @c3y1huang
  • [BACKPORT][v1.7.2][BUG] Test case Stopped replicas on deleted nodes should not be counted as healthy replicas when draining nodes fails 9621 - @yangchiu @derekbit
  • [BUG] robot test case Single Replica Node Down Deletion Policy do-nothing With RWO Volume Replica Locate On Replica Node fails to wait for the volume getting stuck in attaching state 9498 - @c3y1huang
  • [BACKPORT][v1.7.2][BUG] All Backups are lost in the Backup Target if the NFS Service Disconnects and Reconnects again 9542 - @yangchiu @mantissahz
  • [BACKPORT][v1.7.2][BUG] PV Annotation Isn't Updated After Creating An Oversize Volume 9515 - @c3y1huang @chriscchien
  • [BACKPORT][v1.7.2][BUG] Instance manager missing required selector labels after manager crash 9471 - @c3y1huang @chriscchien
  • [BACKPORT][v1.7.2][BUG] Engine Upgrade to 1.7.1 fails on volumes with strict-local data locality 9416 - @yangchiu @james-munson
  • [BACKPORT][v1.7.2][BUG] Longhorn did not close and open encrypted volumes correctly when the service k3s-agent restarted for a while 9387 - @yangchiu @mantissahz
  • [BACKPORT][v1.7.2][BUG] Longhorn keeps resetting my storageClass 9396 - @yangchiu @mantissahz
  • [BACKPORT][v1.7.2][BUG] Fix test case test_rwx_delete_share_manager_pod failure after changes to RWX workload restart. 9505 - @yangchiu @james-munson
  • [BACKPORT][v1.7.2][BUG] Remove unnecessary restart of RWX workload. 9290 - @yangchiu @james-munson
  • [BACKPORT][v1.7.2][BUG] Faulted RWX volume upon creation 9474 - @yangchiu @james-munson
  • [BACKPORT][v1.7.2][BUG] Accidentally encountered a single replica volume backup stuck at progress 17% indefinitely after a node rebooted 9312 - @yangchiu @ChanYiLin
  • [BACKPORT][v1.7.2][BUG] Longhorn thinks node is unschedulable 9382 - @c3y1huang @roger-ryao

Misc

Contributors