Skip to content

v2.12.2

Latest
Latest

Choose a tag to compare

View all tags
@niladrih niladrih released this 06 Oct 08:20
v2.12.2
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: 6th October, 2026

Summary

OpenEBS Replicated PV Mayastor version 2.12.2 is a patch release on top of v2.12.1. It switches Loki's MinIO images to the OpenEBS mirror on Docker Hub, as the upstream images can no longer be pulled anonymously from quay.io. The io-engine and control plane are unchanged from v2.12.1.

This release includes all changes from v2.12.0 and v2.12.1; see their release notes for the features and fixes in the 2.12 line. Upgrading is recommended for anyone on 2.9.0 through 2.12.1 running the chart's default Loki and MinIO setup.

Issues Resolved

Loki MinIO Image Pulls

Resolved an issue where the MinIO pods that serve as Loki's object store could not pull their images. Releases 2.9.0 through 2.12.1 use the minio and mc images from quay.io/minio, which can no longer be pulled anonymously. The chart now uses the docker.io/openebs/minio and docker.io/openebs/mc mirrors, with the same image tags.

Upgrades with kubectl mayastor upgrade carry the existing release's values over to the new chart, and those values hold the old quay.io/minio repositories. The upgrade job now replaces them with the mirror if they are still set to the old defaults. Custom repositories, such as private registry mirrors, are left as they are.

Users who can't upgrade yet can set loki.minio.image.repository=docker.io/openebs/minio and loki.minio.mcImage.repository=docker.io/openebs/mc on their existing release; the mirror carries the image tags used by 2.9.0 through 2.12.1.

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.1...v2.12.2
openebs/mayastor-control-plane@v2.12.1...v2.12.2
openebs/mayastor-extensions@v2.12.1...v2.12.2

Assets 7
Loading