This is unreleased documentation for SUSE® Storage 1.11 (Dev).

Important Notes

Please see here for the full release notes.

Deprecation

V2 Backing Image is deprecated and will be removed in a future release. Users can use containerized data importer (CDI) to import images into SUSE Storage as an alternative. For more information, see SUSE Storage with CDI Imports.

Behavior Change

Cloned Volume Health After Efficient Cloning

With efficient cloning enabled, a newly cloned and detached volume is degraded and has only one replica, with its clone status set to copy-completed-awaiting-healthy. To bring the volume to a healthy state, transition the clone status to completed and rebuild the remaining replica by either enabling offline replica rebuilding or attaching the volume to trigger replica rebuilding. See Issue #12341 and Issue #12328.

General

Kubernetes Version Requirement

Due to the upgrade of the CSI external snapshotter to v8.2.0, you must be running Kubernetes v1.25 or later to upgrade to SUSE Storage v1.8.0 or a newer version.

Upgrade Check Events

When you upgrade with Helm or the Rancher App Marketplace, SUSE Storage performs pre-upgrade checks. If a check fails, the upgrade stops and the reason for the failure is recorded in an event.

For more details, see Upgrading Longhorn Manager.

Manual Checks Before Upgrade

Automated pre-upgrade checks does not cover all scenarios. A manual check is recommended using kubectl or the SUSE Storage UI.

  • Ensure all V2 Data Engine volumes are detached and replicas are stopped. The V2 engine does not support live upgrades.

  • Avoid upgrading when volumes are Faulted. Unusable replicas may be deleted, causing permanent data loss if no backups exist.

  • Avoid upgrading if a failed BackingImage exists. For more information, see Backing Image for details.

  • Create a Longhorn System Backup upgrading is recommended to ensure recoverability.

Scheduling

Replica Scheduling with Balance Algorithm

To improve data distribution and resource utilization, SUSE Storage introduces a balance algorithm that schedules replicas evenly across nodes and disks based on calculated balance scores.

For more information, see Scheduling.

Monitoring

Disk health monitoring

Starting with SUSE Storage v1.11.0, disk health monitoring is available for both the V1 and V2 data engines. SUSE Storage collects disk health data and exposes it through Prometheus metrics and the Node custom resources.

  1. Key features:

    • Automatic health data collection every 10 minutes.

    • Disk health status and detailed attributes exposed as Prometheus metrics.

    • Health data available in the nodes.longhorn.io custom resources.

  • SMART data may not be fully available in virtualized or cloud environments (for example, AWS EBS). This can result in zero values for some attributes.

  • Available health attributes vary depending on disk type and hardware.

For more information, see: Disk health monitoring.

V2 Data Engine

SUSE Storage System Upgrade

Live upgrades of V2 volumes are not supported. Before you upgrade, make sure all V2 volumes are detached.