Skip to content

fix(flux): update chart longhorn 1.10.1 → 1.10.2#31

Merged
truecharts-admin merged 1 commit intomainfrom
renovate/flux-longhorn-1.10.x
Apr 24, 2026
Merged

fix(flux): update chart longhorn 1.10.1 → 1.10.2#31
truecharts-admin merged 1 commit intomainfrom
renovate/flux-longhorn-1.10.x

Conversation

@truecharts-admin
Copy link
Copy Markdown
Contributor

@truecharts-admin truecharts-admin commented Apr 23, 2026

This PR contains the following updates:

Package Update Change
longhorn patch 1.10.11.10.2

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

longhorn/longhorn (longhorn)

v1.10.2: Longhorn v1.10.2

Compare Source

Longhorn v1.10.2 Release Notes

Longhorn 1.10.2 introduces several improvements and bug fixes that are intended to improve system quality, resilience, stability and security.

We welcome feedback and contributions to help continuously improve Longhorn.

For terminology and context on Longhorn releases, see Releases.

[!WARNING]

HotFix

The backing-image-manager:v1.10.2 image is affected by

To mitigate the issues, replace backing-image-manager:v1.10.2 with the hotfixed image backing-image-manager:v1.10.2-hotfix-1.

Follow these steps to apply the update:

  1. Update the backing-image-manager image
    • Change the image tag from v1.10.2 to v1.10.2-hotfix-1 in the appropriate file:
      • For Helm: Update values.yaml
      • For manifests: Update the deployment manifest directly.
  2. Proceed with the upgrade
  • Apply the changes using your standard Helm upgrade command or reapply the updated manifest.

Important Fixes

This release includes several critical stability fixes.

RWX Volume Unavailable After Node Drain

Fixed a race condition where ReadWriteMany (RWX) volumes could remain in the attaching state after node drains, causing workloads to become unavailable.

For more details, see Issue #​12231.

Encrypted Volume Cannot Be Expanded Online

Fixed an issue where online expansion of encrypted volumes did not propagate the new size to the dm-crypt device.

For more details, see Issue #​12368.

Cloned Volume Cannot Be Attached to Workload

Fixed a bug where cloned volumes could fail to reach a healthy state, preventing attachment to workloads.

For more details, see Issue #​12208.

Block Mode Volume Migration Stuck

Fixed a regression in block-mode volume migrations where newly created replicas could incorrectly inherit the lastFailedAt timestamp from source replicas, causing repeated deletion and blocking migration completion.

For more details, see Issue #​12312.

Replica Auto Balance Disk Pressure Threshold Stalled

Fixed an issue where replica auto-balance under disk pressure could be blocked if stopped volumes were present on the disk.

For more details, see Issue #​12334.

Replicas Accumulate During Engine Upgrade

Fixed a bug where temporary replicas could accumulate during engine upgrade. High etcd latency could cause new replicas to fail verification, leading to accumulation over multiple reconciliation cycles.

For more details, see Issue #​12115.

Potential Client Connection and Context Leak

Fixed potential context leaks in the instance manager client and backing image manager client, improving stability and preventing resource exhaustion.

For more details, see Issue #​12200 and Issue #​12195.

Replica Node Level Soft Anti-Affinity Ignored

Fixed a bug of replica scheduling loop where replicas could be scheduled onto nodes that already host a replica, even when Replica Node-Level Soft Anti-Affinity was disabled.

For more details, see Issue #​12251.

Installation

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

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

Feature
  • [BACKPORT][v1.10.2][FEATURE] Inherit namespace for longhorn-share-manager in FastFailover mode 12245 - @​yangchiu
  • [BACKPORT][v1.10.2][FEATURE] [Dependency] aws-sdk-go v1.55.7 is EOL as of 2025-07-31 — plan to migrate to v2? 12181 - @​mantissahz @​roger-ryao
Improvement
Bug

Contributors


Configuration

📅 Schedule: (UTC)

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


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

This PR has been generated by Renovate Bot.

Copy link
Copy Markdown
Member

@Crow-Control Crow-Control left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto approved automated PR

@truecharts-admin truecharts-admin force-pushed the renovate/flux-longhorn-1.10.x branch 3 times, most recently from b3db801 to 84c432e Compare April 24, 2026 01:49
@truecharts-admin truecharts-admin force-pushed the renovate/flux-longhorn-1.10.x branch from 84c432e to 14b8e9d Compare April 24, 2026 01:51
@truecharts-admin truecharts-admin merged commit 55db8b4 into main Apr 24, 2026
8 checks passed
@truecharts-admin truecharts-admin deleted the renovate/flux-longhorn-1.10.x branch April 24, 2026 02:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants