Skip to content

chore(deps): update dependency longhorn/longhorn to v1.11.0#771

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/longhorn-longhorn-1.x
Open

chore(deps): update dependency longhorn/longhorn to v1.11.0#771
renovate[bot] wants to merge 1 commit intomainfrom
renovate/longhorn-longhorn-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 28, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Update Change
longhorn/longhorn minor v1.10.1v1.11.0

Release Notes

longhorn/longhorn (longhorn/longhorn)

v1.11.0: Longhorn v1.11.0

Compare Source

Longhorn v1.11.0 Release Notes

The Longhorn team is excited to announce the release of Longhorn v1.11.0. This release marks a major milestone, with the V2 Data Engine officially entering the Technical Preview stage following significant stability improvements.

Additionally, this version optimizes the stability of the whole system and introduces critical improvements in resource observability, scheduling, and utilization.

For terminology and background on Longhorn releases, see Releases.

[!WARNING]

Hotfix

longhorn-instance-manager Image

The longhorn-instance-manager:v1.11.0 image is affected by a regression issue introduced by the new longhorn-instance-manager Proxy service APIs. The bug causes Proxy connection leaks in the longhorn-instance-manager pods, resulting in increased memory usage. To mitigate this issue, replace longhornio/longhorn-instance-manager:v1.11.0 with the hotfixed image longhornio/longhorn-instance-manager:v1.11.0-hotfix-1.

You can apply the update by following these steps:

  1. Update the longhorn-instance-manager image

    • Change the longhorn-instance-manager image tag from v1.11.0 to v1.11.0-hotfix-1 in the appropriate file:
      • For Helm: Update values.yaml
      • For manifests: Update the deployment manifest directly.
  2. Proceed with the installation or upgrade

    • Apply the changes using your standard Helm install/upgrade command or reapply the updated manifest.

longhorn-manager Image

The longhorn-manager:v1.11.0 image is affected by a regression issue introduced by the new Kubernetes Node validator. The bug blocks setting Kubernetes node CNI labels because it waits for the Longhorn webhook server to be running, while the Longhorn webhook server waits for CNI network to be ready. To mitigate this issue, replace longhornio/longhorn-manager:v1.11.0 with the hotfixed image longhornio/longhorn-manager:v1.11.0-hotfix-1.

You can apply the update by following these steps:

  1. Disable the upgrade version check
  • Helm users: Set upgradeVersionCheck to false in the values.yaml file.

  • Manifest users: Remove the --upgrade-version-check flag from the deployment manifest.

  1. Update the longhorn-manager image
  • Change the longhorn-manager image tag from v1.11.0 to v1.11.0-hotfix-1 in the appropriate file:
    • For Helm: Update values.yaml.

    • For manifests: Update the deployment manifest directly.

  1. Proceed with the installation or upgrade
  • Apply the changes using your standard Helm install/upgrade command or reapply the updated manifest.

Deprecation

V2 Backing Image Deprecation

The Backing Image feature for the V2 Data Engine is now deprecated in v1.11.0 and is scheduled for removal in v1.12.0.

Users using V2 volumes for virtual machines are encouraged to adopt the Containerized Data Importer (CDI) for volume population instead.

GitHub Issue #​12237

Primary Highlights

V2 Data Engine
Now in Technical Preview Stage

We are pleased to announce that the V2 Data Engine has officially graduated to the Technical Preview stage. This indicates increased stability and feature maturity as we move toward General Availability.

Limitation: While the engine is in Technical Preview, live upgrade is not supported yet. V2 volumes must be detached (offline) before engine upgrade.

Support for ublk Frontend

Longhorn supports configuring UBLK performance parameters globally, per volume, or via StorageClass to improve I/O performance.

GitHub Issue #​11039

V1 Data Engine
Faster Replica Rebuilding from Multiple Sources

The V1 Data Engine now supports parallel rebuilding. When a replica needs to be rebuilt, the engine can now stream data from multiple healthy replicas simultaneously rather than a single source. This significantly reduces the time required to restore redundancy for volumes containing tons of scattered data chunks.

GitHub Issue #​11331

General
Balance-Aware Algorithm Disk Selection For Replica Scheduling

Longhorn improves the disk selection for the replica scheduling by introducing an intelligent balance-aware scheduling algorithm, reducing uneven storage usage across nodes and disks.

GitHub Issue #​10512

Node Disk Health Monitoring

Longhorn now actively monitors the physical health of the underlying disks used for storage by using S.M.A.R.T. data. This allows administrators to identify issues and raise alerts when abnormal SMART metrics are detected, helping prevent failed volumes.

GitHub Issue #​12016

Share Manager Networking

Users can now configure an extra network interface for the Share Manager to support complex network segmentation requirements.

GitHub Issue #​10269

ReadWriteOncePod (RWOP) Support

Full support for the Kubernetes ReadWriteOncePod access mode has been added.

GitHub Issue #​9727

StorageClass allowedTopologies Support

Administrators can now use the allowedTopologies field in Longhorn StorageClasses to restrict volume provisioning to specific zones, regions, or nodes within the cluster.

GitHub Issue #​12261

Installation

[!IMPORTANT]
Ensure that your cluster is running Kubernetes v1.25 or later before installing Longhorn v1.11.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.25 or later before upgrading from Longhorn v1.10.x to v1.11.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 in this release

Highlight
Feature
Improvement
Bug
Misc

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 2624533 to 7243400 Compare January 29, 2026 10:11
@renovate renovate bot changed the title chore(deps): update dependency longhorn/longhorn to v1.10.2 chore(deps): update dependency longhorn/longhorn to v1.11.0 Jan 29, 2026
@renovate renovate bot force-pushed the renovate/longhorn-longhorn-1.x branch from 7243400 to 231592d Compare February 2, 2026 20:32
@renovate renovate bot force-pushed the renovate/longhorn-longhorn-1.x branch from 231592d to a85d22b Compare February 12, 2026 12:05
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

Comments