发布日期: 2026-03-13
版本号: v1.11.1

Longhorn v1.11.1 是一个补丁版本，主要针对 V1 和 V2 数据引擎进行了关键错误修复、安全加固和稳定性改进。重点修复了实例管理器中严重的内存泄漏问题，并提升了备份可靠性和卷调度能力。其他重要修复包括解决因 aws-go-sdk v2 引起的备份兼容性问题（如对 S3 兼容存储的支持）、V2 数据引擎（SPDK）功能优化（如快速副本重建和克隆），以及增强 CSI 拓扑感知的 PV 节点亲和性控制。升级和安装前需确保集群运行 Kubernetes v1.25 或更高版本。该版本还解决了引擎升级过程中失败副本累积、备份到 S3 失败、以及内存异常消耗等多个问题，整体提升了系统的可靠性与性能。

更新内容 （中文）

Longhorn v1.11.1 发布说明

Longhorn v1.11.1 是一个补丁版本，重点修复关键错误、加强安全性，并改进 V1 和 V2 数据引擎的稳定性。主要亮点包括修复实例管理器中的重大内存泄漏，以及提升备份可靠性和卷调度能力。

我们欢迎反馈和贡献，以帮助持续改进 Longhorn。

有关 Longhorn 发布的术语和背景，请参阅 发布版本。

重要修复

此版本包含若干关键的稳定性修复。

Longhorn 工作负载 Pod 内存泄漏

修复了一个关键的回归问题，其中 longhorn-instance-manager Pod 中的代理连接泄漏导致了高内存消耗。

更多详情，请参阅 #12575。

备份与恢复兼容性修复

解决了由 aws-go-sdk v2 引入的兼容性问题，包括向 S3 兼容存储（如 Storj 或 Google Cloud Storage）的备份。此修复确保了向远程备份目标传输大量数据时能以正确的授权完成。

更多详情，请参阅 #12714 和 12688。

V2 数据引擎（SPDK）改进

针对部分 V2 数据引擎功能进行了多项增强，包括快速副本重建和克隆。

更多详情，请参阅 #12751 和 12748。

CSI 调度增强

支持 CSI 拓扑感知的 PV nodeAffinity 控制。

更多详情，请参阅 #12689 和 12656。

安装

[!IMPORTANT] 在安装 Longhorn v1.11.1 之前，请确保您的集群运行的是 Kubernetes v1.25 或更高版本。

您可以使用多种工具安装 Longhorn，包括 Rancher、Kubectl 和 Helm。有关安装方法和要求的更多信息，请参阅 Longhorn 文档中的 快速安装。

升级

[!IMPORTANT] 在从 Longhorn v1.10.x 或 v1.11.0 升级到 v1.11.1 之前，请确保您的集群运行的是 Kubernetes v1.25 或更高版本。

[!IMPORTANT] 遇到 longhorn-instance-manager Pod 12575 内存泄漏问题的 v1.11.0 用户，强烈建议升级到 v1.11.1 以获得代理连接泄漏的永久修复。

Longhorn 仅允许从受支持的版本进行升级。有关升级路径和过程的更多信息，请参阅 Longhorn 文档中的 升级。

发布后已知问题

有关此发布后发现的问题信息，请参阅 发布已知问题。

此版本已解决的问题

改进

  • [BACKPORT][v1.11.1][改进] 确保 V2 引擎的 ReplicaAdd 尊重 fast-replica-rebuild-enabled 设置 12751 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][改进] 拓扑感知 PV nodeAffinity 控制：allowedTopologies 键 + strictTopology 12689 - @hookak @roger-ryao
  • [BACKPORT][v1.11.1][改进] 为节点控制器删除基础镜像副本的原因提供详细日志 12585 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.11.1][改进] 放宽 endpoint-network-for-rwx-volume 对可迁移块模式卷的验证 12711 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][改进] 为 csi-resizer 提供 RBAC 权限 12694 - @yangchiu

错误

  • [BACKPORT][v1.11.1][错误] 引擎升级期间失败副本累积 12768 - @davidcheng0922
  • [BACKPORT][v1.11.1][错误] V2 卷克隆状态随时间变化 12748 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][错误] 备份到 S3 在 95% 处失败 12714 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][错误] spdk_tgt 在 CI 测试运行期间于 longhorn-spdk-helper 中遇到断言失败 12738 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][错误] 由于 AWS SDK Go v2 CRC32 校验和不兼容，Google Cloud Storage (GCS) 备份目标总是因 SignatureDoesNotMatch 而失败 12688 - @mantissahz @chriscchien
  • [BACKPORT][v1.11.1][错误] 启用设置 defaultSettings.nodeDiskHealthMonitoring 12730 - @chriscchien
  • [BACKPORT][v1.11.1][错误] nsmounter get_pid 中的陈旧 name 变量 12704 - @chriscchien
  • [BACKPORT][v1.11.1][错误] 升级到 1.11.0 后，新的持久卷具有 nodeAffinity 12665 - @chriscchien
  • [BACKPORT][v1.11.1][错误] 当同一节点上存在多个副本时，不正确的存储双重计数导致调度失败 12661 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.1][错误] 以相同名称重新创建的块磁盘在卷和磁盘删除后永远无法被调度 12641 - @davidcheng0922
  • [BACKPORT][v1.11.1][错误] Longhorn v1.10 卷 API 与 v1.8.1 清单不兼容 12618 - @mantissahz @roger-ryao
  • [BACKPORT][v1.11.1][错误] [v2] 无法使用分区作为块设备 12626 - @bachmanity1
  • [BACKPORT][v1.11.1][错误] 升级到 v1.10.x 及更高版本后，Volume.Spec.CloneMode 为空 12615 - @mantissahz
  • [BACKPORT][v1.11.1][错误] Longhorn 验证 webhook 阻止 k3s 服务器节点加入 - flannel CNI 初始化失败 12589 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][错误] v1.11.0 实例管理器内存消耗非常高 12575 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][错误] 启用 HTTP 代理时，基础镜像数据源 Pod 失败 12780 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][错误] 在多实例管理器节点上，孤立控制器未清理相应实例管理器上的实例 12788 - @COLDTURNIP @roger-ryao

稳定性

  • [BACKPORT][v1.11.1][错误] 卷指标收集器中潜在的 NEP 12733 - @derekbit @chriscchien

贡献者

  • @COLDTURNIP
  • @PhanLe1010
  • @bachmanity1
  • @c3y1huang
  • @chriscchien
  • @davidcheng0922
  • @derekbit
  • @forbesguthrie
  • @github-actions[bot]
  • @hookak
  • @houhoucoop
  • @innobead
  • @mantissahz
  • @rebeccazzzz
  • @roger-ryao
  • @shuo-wu
  • @sushant-suse
  • @yangchiu

更新内容 （原始）

Longhorn v1.11.1 Release Notes

Longhorn v1.11.1 is a patch release that focuses on critical bug fixes, security hardening, and stability improvements for both V1 and V2 data engines. Key highlights include a fix for a significant memory leak in the instance manager and improvements to backup reliability and volume scheduling.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

Important Fixes

This release includes several critical stability fixes.

Longhorn workload pods memory leak

Fixed a critical regression where proxy connection leaks in the longhorn-instance-manager pods caused high memory consumption.

For more details, see #12575

Backup & Restore compatibility fix

Resolved compatibility issues introduced by aws-go-sdk v2, including backups to S3-compatible storage (like Storj or Google Cloud Storage). This fix ensures the completion of large data transfers to remote backup targets with correct authorization.

For more details, see #12714 and 12688

V2 Data Engine (SPDK) refinements

Several enhancements were delivered for some V2 Data Engine features, including fast replica rebuild and clone.

For more details, see #12751 and 12748

CSI scheduling enhancement

Support CSI topology-aware PV nodeAffinity control.

For more details, see #12689 and 12656

Installation

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

[!IMPORTANT] Users on v1.11.0 who experienced the memory leaks of longhorn-instance-manager pods 12575 are highly encouraged to upgrade to v1.11.1 to receive the permanent fix for the proxy connection leaks.

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

Improvement

  • [BACKPORT][v1.11.1][IMPROVEMENT] Ensure V2 Engine ReplicaAdd respects the fast-replica-rebuild-enabled setting 12751 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] Topology-aware PV nodeAffinity control: allowedTopologies keys + strictTopology 12689 - @hookak @roger-ryao
  • [BACKPORT][v1.11.1][IMPROVEMENT] detailed log for the reason of node controller deleting backing image copies 12585 - @COLDTURNIP @yangchiu
  • [BACKPORT][v1.11.1][IMPROVEMENT] Relax endpoint-network-for-rwx-volume validation for migratable block-mode volumes 12711 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][IMPROVEMENT] RBAC permissions for csi-resizer 12694 - @yangchiu

Bug

  • [BACKPORT][v1.11.1][BUG] Failed replicas accumulate during engine upgrade 12768 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] V2 Volume Clone Status is Changed Over Time 12748 - @davidcheng0922 @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backup to S3 fails at 95% 12714 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] spdk_tgt encountered an assertion failure in longhorn-spdk-helper during a CI test run 12738 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Google Cloud Storage (GCS) backup target always fails with SignatureDoesNotMatch due to AWS SDK Go v2 CRC32 checksum incompatibility 12688 - @mantissahz @chriscchien
  • [BACKPORT][v1.11.1][BUG] Enable to set defaultSettings.nodeDiskHealthMonitoring 12730 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] stale name variable in nsmounter get_pid 12704 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] After upgrading to 1.11.0, new persistent volumes have nodeAffinity 12665 - @chriscchien
  • [BACKPORT][v1.11.1][BUG] Incorrect storage double-counting causes scheduling failure when multiple replicas exist on the same node 12661 - @yangchiu @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Recreated block disk with same name never becomes schedulable after volume and disk deletion 12641 - @davidcheng0922
  • [BACKPORT][v1.11.1][BUG] Longhorn v1.10 Volume API is not compatible with the v1.8.1 manifest 12618 - @mantissahz @roger-ryao
  • [BACKPORT][v1.11.1][BUG] [v2] Can’t use partition as block device 12626 - @bachmanity1
  • [BACKPORT][v1.11.1][BUG] Volume.Spec.CloneMode is empty after upgrading to v1.10.x and following version 12615 - @mantissahz
  • [BACKPORT][v1.11.1][BUG] Longhorn validating webhook blocks k3s server node joins - flannel CNI fails to initialize 12589 - @yangchiu @mantissahz
  • [BACKPORT][v1.11.1][BUG] V1.11.0 very high memory consumption for instance manager 12575 - @derekbit @roger-ryao
  • [BACKPORT][v1.11.1][BUG] Backing image data source pod fails when HTTP proxy is enabled 12780 - @c3y1huang @chriscchien
  • [BACKPORT][v1.11.1][BUG] orphan controller does not cleanup the instance on the corresponding instance manager on a multiple IM node 12788 - @COLDTURNIP @roger-ryao

Stability

  • [BACKPORT][v1.11.1][BUG] Potential NEP in Volume Metrics Collector 12733 - @derekbit @chriscchien

Contributors

  • @COLDTURNIP
  • @PhanLe1010
  • @bachmanity1
  • @c3y1huang
  • @chriscchien
  • @davidcheng0922
  • @derekbit
  • @forbesguthrie
  • @github-actions[bot]
  • @hookak
  • @houhoucoop
  • @innobead
  • @mantissahz
  • @rebeccazzzz
  • @roger-ryao
  • @shuo-wu
  • @sushant-suse
  • @yangchiu

下载链接