Skip to content

v2.12.1

Latest
Latest

Choose a tag to compare

View all tags
@Abhinandan-Purkait Abhinandan-Purkait released this 09 Sep 05:44
v2.12.1
53b43d2
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Release Date: 9th September, 2026

Summary

OpenEBS Replicated PV Mayastor version 2.12.1 is a patch release on top of v2.12.0, delivering targeted fixes and minor enhancements.

Enhancements

Plugin Output Improvements

The kubectl mayastor plugin output now includes an ID column, and spurious error strings have been silenced from the output.

Issues Resolved

Label Routes with Slashes

Resolved an issue where labels containing slashes (such as Kubernetes-style domain/key labels) were rejected by the delete, cordon, and drain REST routes.

Supportability Loki Auto-Discovery Timeout

Resolved an issue where Loki auto-discovery could time out while collecting a support bundle; the default --timeout has also been raised.

Testing

Mayastor is subject to extensive unit, component and system-level testing throughout the development and release cycle. Resources for system-level (E2E) testing are currently provided by DataCore Software.

At this time, personnel and hardware resource limitations constrain testing by the maintainers to linux builds on x86. This reflects the primary use-case which the maintainers are currently targeting with the OpenEBS Mayastor project. Therefore, the use of Mayastor with other operating systems and/or architectures, if even possible, should be considered serendipitous and wholly experimental.

This release has been subject to End-to-End testing under Ubuntu 22.04 LTS (kernel: ubuntu-6.8.0-90-generic)

  • Tested k8s versions
    • 1.32.10
    • 1.35.6

Known Behavioural Limitations

  • The IO engine fully utilizes all allocated CPU cores regardless of the actual I/O load, as it runs a poller at full speed.

NOTE: An experimental implementation of interrupt mode support is available.

  • Each DiskPool is limited to a single block device and cannot span across multiple devices.
  • The data-at-rest encryption feature does not support rotation of Data Encryption Keys (DEKs).

Known Issues

  • If a node hosting a pod reboots and the pod lacks a controller (like a Deployment), the volume unpublish operation may not trigger. This causes the control plane to assume the volume is still in use, which leads to fsfreeze operation failure during snapshots.
    Workaround: Recreate or rebind the pod to ensure proper volume mounting.
  • Large pools (Example: 10–20TiB) may take a while during recovery after a dirty shutdown of the node hosting the io-engine.

Full Changelog:
v2.12.0...v2.12.1
openebs/mayastor-control-plane@v2.12.0...v2.12.1
openebs/mayastor-extensions@v2.12.0...v2.12.1

Assets 7
Loading