Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency longhorn/longhorn to v1.7.2 #10

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 23, 2024

This PR contains the following updates:

Package Update Change
longhorn/longhorn minor v1.6.1 -> v1.7.2

Release Notes

longhorn/longhorn (longhorn/longhorn)

v1.7.2: Longhorn v1.7.2

Compare 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.

[!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

Misc

Contributors

v1.7.1: Longhorn v1.7.1

Compare 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.

[!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.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

[!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.1.

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

Contributors

v1.7.0: Longhorn v1.7.0

Compare 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.

[!WARNING]
The Longhorn team has identified a critical issue that affects volume attachment in Longhorn v1.7.0. We are currently working on releasing v1.7.1, which will be available soon. If your Longhorn cluster contains engine resources with names in the format <volume name>-e-<8-char random id> that are created before v1.5.2 and v1.4.4, please put v1.7.0 upgrade on hold until v1.7.1 is available.

You can use the following command to check if it is safe to upgrade your Longhorn cluster to v1.7.0:

[ $(kubectl -n longhorn-system get engines.longhorn.io -o name | grep -E '\-e\-[a-z0-9]{8}$' | wc -l) -gt 0 ] && echo "Please hold off on upgrading to v1.7.0 until v1.7.1 is available." || echo "Safe to upgrade to v1.7.0."

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

[!IMPORTANT]
Ensure that your cluster is running Kubernetes v1.21 or later before installing Longhorn v1.7.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.21 or later before upgrading from Longhorn v1.6.x to v1.7.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.

Resolved Issues

Highlights
Features
Improvements
Bug Fixes

Configuration

📅 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/longhorn-longhorn-1.x branch from 3e98352 to b59fd3a Compare August 20, 2024 13:07
@renovate renovate bot changed the title chore(deps): update dependency longhorn/longhorn to v1.6.2 chore(deps): update dependency longhorn/longhorn to v1.7.0 Aug 20, 2024
@renovate renovate bot force-pushed the renovate/longhorn-longhorn-1.x branch from b59fd3a to 445b6df Compare September 4, 2024 11:34
@renovate renovate bot changed the title chore(deps): update dependency longhorn/longhorn to v1.7.0 chore(deps): update dependency longhorn/longhorn to v1.7.1 Sep 4, 2024
@renovate renovate bot force-pushed the renovate/longhorn-longhorn-1.x branch from 445b6df to c4b50e3 Compare October 18, 2024 08:29
@renovate renovate bot changed the title chore(deps): update dependency longhorn/longhorn to v1.7.1 chore(deps): update dependency longhorn/longhorn to v1.7.2 Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants