Update dependency https://github.com/longhorn/longhorn to v1.4.0-rc3 #49
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/https-github.com-longhorn-longhorn-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.4.0-rc1->v1.4.0-rc3Release Notes
longhorn/longhorn
v1.4.0-rc3Compare Source
Release Note
v1.4.0-rc3 released! 🎆
This release introduces many enhancements, improvements, and bug fixes as described below about stability, performance, data integrity, troubleshooting, and so on. Please try it and feedback. Thanks for all the contributions!
Kubernetes 1.25 Support [doc]
In the previous versions, Longhorn relies on Pod Security Policy (PSP) to authorize Longhorn components for privileged operations. From Kubernetes 1.25, PSP has been removed and replaced with Pod Security Admission (PSA). Longhorn v1.4.0 supports opt-in PSP enablement, so it can support Kubernetes versions with or without PSP.
ARM64 GA
ARM64 has been experimental from Longhorn v1.1.0. After receiving more user feedback and increasing testing coverage, ARM64 distribution has been stabilized with quality as per our regular regression testing, so it is qualified for general availability.
RWX GA [lep][doc]
RWX has been experimental from Longhorn v1.1.0, but it lacks availability support when the Longhorn Share Manager component behind becomes unavailable. Longhorn v1.4.0 supports NFS recovery backend based on Kubernetes built-in resource, ConfigMap, for recovering NFS client connection during the fail-over period. Also, the NFS client hard mode introduction will further avoid previous potential data loss. For the detail, please check the issue and enhancement proposal.
Volume Snapshot Checksum [lep][doc]
Data integrity is a continuous effort for Longhorn. In this version, Snapshot Checksum has been introduced w/ some settings to allow users to enable or disable checksum calculation with different modes.
Volume Bit-rot Protection [lep][doc]
When enabling the Volume Snapshot Checksum feature, Longhorn will periodically calculate and check the checksums of volume snapshots, find corrupted snapshots, then fix them.
Volume Replica Rebuilding Speedup
When enabling the Volume Snapshot Checksum feature, Longhorn will use the calculated snapshot checksum to avoid needless snapshot replication between nodes for improving replica rebuilding speed and resource consumption.
Volume Trim [lep][doc]
Longhorn engine supports UNMAP SCSI command to reclaim space from the block volume.
Online Volume Expansion
Longhorn engine supports optional parameters to pass size expansion requests when updating the volume frontend to support online volume expansion and resize the filesystem via CSI node driver.
Local Volume via Data Locality Strict Mode [lep][doc]
Local volume is based on a new Data Locality setting, Strict Local. It will allow users to create one replica volume staying in a consistent location, and the data transfer between the volume frontend and engine will be through a local socket instead of the TCP stack to improve performance and reduce resource consumption.
Volume Recurring Job Backup Restore [lep][doc]
Recurring jobs binding to a volume can be backed up to the remote backup target together with the volume backup metadata. They can be restored back as well for a better operation experience.
Volume IO Metrics [doc]
Longhorn enriches Volume metrics by providing real-time IO stats including IOPS, latency, and throughput of R/W IO. Users can set up a monotoning solution like Prometheus to monitor volume performance.
Longhorn System Backup & Restore [lep][doc]
Users can back up the longhorn system to the remote backup target. Afterward, it's able to restore back to an existing cluster in place or a new cluster for specific operational purposes.
Support Bundle Enhancement [lep]
Longhorn introduces a new support bundle integration based on a general support bundle kit solution. This can help us collect more complete troubleshooting info and simulate the cluster environment.
Tunable Timeout between Engine and Replica [doc]
In the current Longhorn versions, the default timeout between the Longhorn engine and replica is fixed without any exposed user settings. This will potentially bring some challenges for users having a low-spec infra environment. By exporting the setting configurable, it will allow users adaptively tune the stability of volume operations.
Installation
Longhorn supports 3 installation ways including Rancher App Marketplace, Kubectl, and Helm. Follow the installation instructions here.
Upgrade
The live upgrade from v1.3.x is not supported until the GA release. When available, follow the upgrade instructions here. here.
Deprecation & Incompatibilities
Known Issues after Release
Please follow up on here about any outstanding issues found after this release.
Highlights
Enhancements
Improvement
Performance
Stability
Bugs
Misc
Contributors
v1.4.0-rc2Compare Source
Release Note
v1.4.0-rc2 released! 🎆
This release introduces many enhancements, improvements, and bug fixes as described below about stability, performance, data integrity, troubleshooting, and so on. Please try it and feedback. Thanks for all the contributions!
Kubernetes 1.25 Support [doc]
In the previous versions, Longhorn relies on Pod Security Policy (PSP) to authorize Longhorn components for privileged operations. From Kubernetes 1.25, PSP has been removed and replaced with Pod Security Admission (PSA). Longhorn v1.4.0 supports opt-in PSP enablement, so it can support Kubernetes versions with or without PSP.
ARM64 GA
ARM64 has been experimental from Longhorn v1.1.0. After receiving more user feedback and increasing testing coverage, ARM64 distribution has been stabilized with quality as per our regular regression testing, so it is qualified for general availability.
RWX GA [lep][doc]
RWX has been experimental from Longhorn v1.1.0, but it lacks availability support when the Longhorn Share Manager component behind becomes unavailable. Longhorn v1.4.0 supports NFS recovery backend based on Kubernetes built-in resource, ConfigMap, for recovering NFS client connection during the fail-over period. Also, the NFS client hard mode introduction will further avoid previous potential data loss. For the detail, please check the issue and enhancement proposal.
Volume Snapshot Checksum [lep][doc]
Data integrity is a continuous effort for Longhorn. In this version, Snapshot Checksum has been introduced w/ some settings to allow users to enable or disable checksum calculation with different modes.
Volume Bit-rot Protection [lep][doc]
When enabling the Volume Snapshot Checksum feature, Longhorn will periodically calculate and check the checksums of volume snapshots, find corrupted snapshots, then fix them.
Volume Replica Rebuilding Speedup
When enabling the Volume Snapshot Checksum feature, Longhorn will use the calculated snapshot checksum to avoid needless snapshot replication between nodes for improving replica rebuilding speed and resource consumption.
Volume Trim [lep][doc]
Longhorn engine supports UNMAP SCSI command to reclaim space from the block volume.
Online Volume Expansion
Longhorn engine supports optional parameters to pass size expansion requests when updating the volume frontend to support online volume expansion and resize the filesystem via CSI node driver.
Local Volume via Data Locality Strict Mode [lep][doc]
Local volume is based on a new Data Locality setting, Strict Local. It will allow users to create one replica volume staying in a consistent location, and the data transfer between the volume frontend and engine will be through a local socket instead of the TCP stack to improve performance and reduce resource consumption.
Volume Recurring Job Backup Restore [lep][doc]
Recurring jobs binding to a volume can be backed up to the remote backup target together with the volume backup metadata. They can be restored back as well for a better operation experience.
Volume IO Metrics
Longhorn enriches Volume metrics by providing real-time IO stats including IOPS, latency, and throughput of R/W IO. Users can set up a monotoning solution like Prometheus to monitor volume performance.
Longhorn System Backup & Restore [lep]
Users can back up the longhorn system to the remote backup target. Afterward, it's able to restore back to an existing cluster in place or a new cluster for specific operational purposes.
Support Bundle Enhancement[lep]
Longhorn introduces a new support bundle integration based on a general support bundle kit solution. This can help us collect more complete troubleshooting info and simulate the cluster environment.
Tunable Timeout between Engine and Replica [doc]
In the current Longhorn versions, the default timeout between the Longhorn engine and replica is fixed without any exposed user settings. This will potentially bring some challenges for users having a low-spec infra environment. By exporting the setting configurable, it will allow users adaptively tune the stability of volume operations.
Installation
Longhorn supports 3 installation ways including Rancher App Marketplace, Kubectl, and Helm. Follow the installation instructions here.
Upgrade
The live upgrade from v1.3.x is not supported until the GA release. When available, follow the upgrade instructions here. here.
Deprecation & Incompatibilities
Known Issues after Release
Please follow up on here about any outstanding issues found after this release.
Highlights
Enhancements
Improvement
Performance
Stability
Bugs
Misc
Contributors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Renovate Bot.
Renovate Ignore Notification
As this PR has been closed unmerged, Renovate will now ignore this update (v1.4.0-rc3). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the
ignoreDepsarray of your renovate config.If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.
Pull request closed