Releases · longhorn/longhorn · GitHub

Longhorn v1.9.1 Release Notes Longhorn 1.9.1 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. NoteFor more information about release-related terminology, see Releases. Installation ImportantEnsure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.9.1. 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 ImportantEnsure that your cluster is running Kubernetes v1.25 or later before upgrading from Longhorn v1.8.x or v1.9.x (< v1.9.1) to v1.9.1. 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 Feature [BACKPORT][v1.9.1][FEATURE] Standardized way to override container image registry 11068 - @marcosbc @roger-ryao [BACKPORT][v1.9.1][FEATURE] Standardized way to specify image pull secrets 11072 - @marcosbc @chriscchien Improvement [BACKPORT][v1.9.1][IMPROVEMENT] Remove the Patch preserveUnknownFields: false for CRDs 11280 - @derekbit @chriscchien [BACKPORT][v1.9.1][IMPROVEMENT] Improve the disk space un-schedulable condition message 11212 - @yangchiu @davidcheng0922 [BACKPORT][v1.9.1][IMPROVEMENT] Improve the condition message of engine image check 11196 - @derekbit @chriscchien [BACKPORT][v1.9.1][IMPROVEMENT] Improve the logging when detecting multiple backup volumes of the same volume on the same backup target 11225 - @PhanLe1010 @chriscchien [BACKPORT][v1.9.1][IMPROVEMENT] extra invalid BackupVolumeCR may be created during cluster split-brain 11168 - @mantissahz @rog