github longhorn/longhorn v1.1.1
Longhorn v1.1.1 Release

latest releases: v1.5.5-rc2, v1.5.5-rc1, v1.6.1...
2 years ago

v1.1.1 released! 🎆

There are many new features, enhancements, and bug fixes including different areas as below. Especially, most of the major items are driven by community users to enhance and improve Longhorn functionalities and stability. Thanks for all the contributions!

  • Automatic Longhorn Engine Upgrade
    • Before v1.1.1, for live engine image upgrade, users only can manually upgrade the engine image of each healthy volume. v1.1.1 supports this to avoid needless user intervention [doc]
  • Virtual Machine Volume Support
    • Virtual machine volume creation by Longhorn backing image [doc]
    • Backing image management native support without any 3rd-party image repository [LEP]
    • Virtual machine live migration support by Longhorn migratable RWO volume [LEP]
    • Ability to use as a volume storage service by virtualization orchestration solutions like Harvester
  • Granular Resource Reservation for Longhorn Engine/Replica
    • Before v1.1.1, users only can configure a global setting for CPU resource reservation for each engine/replica. v1.1.1 supports granular node-specific settings for each engine/replica individually. [doc]
  • AWS IAM Role Support to Generate Temporary AWS credentials
    • Besides using IAM user credentials, v1.1.1 allows users to configure IAM Assume Role to generate temporary credentials by AWS security token service to do the backup and restore operations. [doc]
  • Longhorn Frontend WebSocket Performance Enhancement to Improve User Experience
    • Improves the UI performance to adopt event-driven data update to reduce needless network traffic caused by frequently pulling the updated info from the backend.
  • Dependency Installation Manifests for Node Prerequisites
    • Comes out with some installation manifests for prerequisites (like iSCSI and NFS client libraries). It's not integrated into the Longhorn installation process, but it's optional and helpful for users to prepare the environment ready for Longhorn.

Installation

Longhorn supports 3 installation ways including Rancher catalog, Kubectl, and Helm. Follow the installation instructions here.

Upgrade

Follow the upgrade instructions here.

Automatic Longhorn Engine Upgrade supported

Besides manually upgrading Longhorn engines, it's able to do automatic engine upgrades with configurable settings and conditions.

Concurrent Automatic Engine Upgrade Per Node Limit Setting

  • Controls the maximum number of engines per node that are allowed to automatically upgrade to the default engine image at the same time. The default value is 0, so Longhorn will not automatically upgrade volumes’ engines to the default version by default. If configured, we recommend setting the value to 3 to leave some room for error but don’t overwhelm the system with too many failed upgrades. [doc]

Conditions of Automatic Engine Upgrade

If the value of Concurrent Automatic Engine Upgrade Per Node Limit Setting is bigger than 0, in the below conditions, the automatic engine upgrade will happen.

  • Healthy attached volumes - Live upgrade
  • Detached volumes - Offline upgrade

But, Longhorn doesn’t automatically upgrade disaster recovery volumes to the new default engine image because it would trigger a full restoration for the disaster recovery volumes. The full restoration might affect the performance of other running Longhorn volumes in the system, so we leave it to users to decide to do manual engine upgrades at the appropriate time. For the detailed, check [doc]

Engine Manager CPU Request and Replica Manager CPU Request introduced, but Guaranteed Engine CPU deprecated

The new node-specific Engine Manager CPU Request and Replica Manager CPU Request reservations are introduced, and the existing Guaranteed Engine CPU gets deprecated. To avoid crashing existing volumes after Longhorn Manager upgrade, the deprecated setting Guaranteed Engine CPU will be automatically set Engine Manager CPU Request and Replica Manager CPU Request from each node based on the deprecated setting value during the upgrade. Then, the new global instance manager CPU settings Guaranteed Engine Manager CPU and Guaranteed Replica Manager CPU won’t take effect.

For the detailed, check [doc: post-upgrade], [doc: guaranteed-engine-manager-cpu], and [doc: guaranteed-replica-manager-cpu]

Highlights

Enhancements

Bugs

Misc

Contributors

Thanks to all contributors!

Don't miss a new longhorn release

NewReleases is sending notifications on new releases.