chore(deps): update dependency longhorn/longhorn to v1.7.2 #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.6.1
->v1.7.2
Release Notes
longhorn/longhorn (longhorn/longhorn)
v1.7.2
: Longhorn v1.7.2Compare Source
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.
Installation
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
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
dm_crypt
on host machines 9317 - @yangchiu @mantissahzBug
Stopped replicas on deleted nodes should not be counted as healthy replicas when draining nodes
fails 9621 - @yangchiu @derekbitSingle 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 - @c3y1huangMisc
Contributors
v1.7.1
: Longhorn v1.7.1Compare Source
Longhorn v1.7.1 Release Notes
Longhorn 1.7.1 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.
Installation
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
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
cryptsetup
9316 - @mantissahz @roger-ryaodm_crypt
on host machines 9310 - @mantissahzBug
Always
9333 - @c3y1huang @roger-ryaoContributors
v1.7.0
: Longhorn v1.7.0Compare Source
Longhorn v1.7.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, platform-agnostic deployment, high availability, and improvements to data protection, stability, performance, and resilience.
The Longhorn team appreciates your contributions and anticipates receiving feedback regarding this release.
For more information about release-related terminology, see Releases.
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.
Primary Highlights
New V2 Data Engine Features
Although the V2 Data Engine is still considered a preview feature in this release, the core functions have been significantly enhanced.
The Longhorn team will continue to develop features for the V1 Data Engine and to prepare the V2 Data Engine for use in all types of environments.
Platform-Agnostic Deployment
Longhorn is designed to seamlessly operate on general-purpose Linux distributions and certain container-optimized operating systems. v1.7.0 provides robust and efficient persistent storage solutions for Kubernetes clusters running on Container-Optimized OS (COS).
High Availability
v1.7.0 introduces features that enhance system resilience and address potential single points of failure.
Data Protection
Starting with v1.7.0, Longhorn supports periodic and on-demand full backups that help reduce the likelihood of backup corruption and enhance the overall reliability of the backup process.
Scheduling
The replica auto-balancing feature was enhanced to address disk space pressure from growing volumes. These enhancements reduce manual intervention by automatically rebalancing replicas under disk pressure and improve performance with faster replica rebuilding through local file copying.
Storage Network
The storage network now(https://redirect.github.com/longhorn/longhorn/issues/8184)orn/longhorn/issues/8184\)) with network segregation, enabling dedicated traffic lanes for storage operations.
Longhorn CLI
The Longhorn CLI, which is the official Longhorn command line tool, is introduced in v1.7.0. This tool interacts with Longhorn by creating Kubernetes custom resources (CRs) and executing commands inside a dedicated pod for in-cluster and host operations. Usage scenarios include installation, operations such as exporting replicas, and troubleshooting.
Installation
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
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
Highlights
fsfreeze
instead ofsync
before snapshot 2187 - @ejweber @chriscchienFeatures
Improvements
UserCreated
flag 7578 - @DamiaSan @roger-ryaoSettingDefinition
7441 - @ChanYiLin @roger-ryaonode.spec.diskStatus
8458 - @derekbit @chriscchienquay.io/openshift/origin-oauth-proxy
image to Longhorn repo similar to what we are doing for CSI sidecar images 8329 - @PhanLe1010 @roger-ryaoContent-Length
of an resource via URL 7892 - @votdev @chriscchienBug Fixes
uio_pci_generic
9182 - @derekbitlonghornctl
doesn't work onamazon linux
andsle-micro
9139 - @mantissahz @chriscchientest_system_backup_and_restore_volume_with_backingimage
failed on sle-micro ARM64 9209 - @ChanYiLintest_support_bundle_should_not_timeout
support bundle cleanup failed 9055 - @yangchiu @mantissahztest_csi_encrypted_block_volume
failed even thoughcryptsetup
has been installed 9000 - @ejweber @roger-ryaotest_engine_image_not_fully_deployed_perform_auto_upgrade_engine
failed due to engine image unable to deploy on one of nodes 9038 - @yangchiu @mantissahztest_allow_volume_creation_with_degraded_availability_csi
failed due to inconsistentScheduled
status 9035 - @yangchiu @ejweberstorage-network-for-rwx-volume-enabled
when RWX volume attached 8979 - @c3y1huang @chriscchienConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.