feat(helm): update openebs ( 4.1.1 → 4.3.0 )

[renovate]

This PR contains the following updates:

Package	Update	Change
openebs (source)	minor	4.1.1 -> 4.3.0

---

Release Notes

openebs/openebs (openebs)

v4.3.0

Compare Source

OpenEBS 4.3.0 Release Notes

Release Summary

OpenEBS version 4.3 introduces several functional fixes and new features focused on improving Data Security, User Experience, High availability (HA), replica rebuilds, and overall stability. The key highlights are Mayastor's support for At-Rest data encryption and a new Openebs plugin thats allows users to interact with all engines supplied by OpenEBS project. In addition, the release includes various usability and functional fixes for mayastor, ZFS, LocalPV LVM and LocalPV Hostpath provisioners, along with documentation enhancements to help users and new contributors get started quickly.

Change Summary

kubectl openebs plugin

• With this umbrella plugin, OpenEBS users who have installed cluster using OpenEBS umbrella chart will be able to interface all engines i.e Mayastor, localpv-lvm, localpv-zfs, hostpath using a single plugin.

Local Storage

ZFS Enhancements:

• Introduced a backup garbage collector in the controller to automatically clean up stale or orphaned backup resources.
• Updated CSI spec and associated sidecar containers to CSI v1.11.
• Added improved and consistent labeling, including logging-related labels, to enhance Helm chart maintainability and observability.

ZFS Fixes:

• Fixed an issue where the quota property was not correctly retained during upgrades.
• Ensured backward compatibility of quotatype values during volume restores.
• Fixed a crash where unhandled errors in the CSI NodeGetInfo call could cause the controller to exit unexpectedly.
• The gRPC server now gracefully handles SIGTERM and SIGINT signals for clean exit.
• The agent now leverages the OpenEBS lib-csi Kubernetes client to reliably load kubeconfig from multiple locations.
• The CLI flag --plugin now only accepts controller and agent, disallowing invalid values like node.

LVM Enhancements:

• Added support for formatOptions via storage class. These options will be used when formatting the device using mkfs tool.
• Excludes Kubernetes cordoned nodes while provisioning volumes.
• Updated CSI spec to v1.9 and associated sidecar images.

LocalPV Hostpath Improvements:

• Fixed a scenario where a pod crashes when creating an init pod; new pods always failed because the init pod already existed.
• Added support to specify file permissions for PVC hostpaths.

LocalPV Release Notes

LocalPV-ZFS:

Refer to the LocalPV-ZFS v2.8.0 release for detailed changes.

LocalPV-LVM:

Refer to the LocalPV-LVM v1.7.0 release for detailed changes.

LocalPV Hostpath:

Refer to the LocalPV Hostpath v4.3.0 release for detailed changes.

Known Issues for LocalPV

Controller Pod Restart on Single Node Setups:
After upgrading, single node setups may face issues where the ZFS-localpv/LVM-localpv controller pod does not enter the Running state due to changes in the controller manifest (now a Deployment) and missing affinity rules.

Workaround: Delete the old controller pod to allow the new pod to be scheduled correctly. This does not happen if upgrading from the previous release of ZFS-localpv/LVM-localpv.

Thin pool issue with LocalPV-LVM
We do not unmap/reclaim Thin pool capacity. It is not tracked in lvmnode cr also which can cause unexpected behaviour when working with thin volumes. Refer (When using lvm thinpool type, csistoragecapacities calculation is incorrect · Issue #​382 · openebs/lvm-localpv)

Limitations for LocalPV

LocalPV-LVM:

LVM-localpv has support for volume snapshot. But it doesn't support restore from a snapshot yet. It is in our roadmap.

Replicated Storage (Mayastor)

Support for at-rest data encryption:

OpenEBS offers support for data-at-rest encryption to help ensure the confidentiality of persistent data stored on disk.

With this capability, any disk pool configured with a user-defined encryption key can host encrypted volume replicas.

This feature is particularly beneficial in environments requiring compliance with regulatory or security standards.

Additional Enhancements:

• Added support for IPv6.
• Added support for formatOptions via storage class.
• Prefers cordoned nodes while removing volumes replicas eg. volume scale down.
• We now restrict pool creation using non-persistent devlinks (/dev/sdX).
• User do not have to recreate SC while restoring volume from thick snapshot. This fix was important for CSI based backup operations.
• Add new volume health information to better showcase what the current state of the volume is.
• Added a plugin command to delete volume. Mainly applicable for a PVC with RETAIN policy where user can end up in a situation where mayastor may have a volume without a PV object.
• Avoid full rebuild if partial rebuild call fails due to the max rebuild limit.

Upgrade and Backward Incompatibilities

Kubernetes Requirement: Kubernetes 1.23 or higher is recommended.

Engine Compatibility: Upgrades to OpenEBS 4.3.0 are supported only for the following engines:

• Local PV Hostpath
• Local PV LVM
• Local PV ZFS
• Mayastor (from earlier editions, 3.10.x or below)

Replicated PV Mayastor Release Notes

Refer to the Mayastor v2.9.0 release for detailed changes.

Known Behavioural Limitations

• The Mayastor IO engine fully utilizes allocated CPU cores regardless of I/O load, running a poller at full speed.
• A Mayastor DiskPool is limited to a single block device and cannot span multiple block devices.
• The new at-rest encryption feature does not support rotating Data Encryption Keys(DEK).

Known Issues - Replicated PV (Mayastor)

DiskPool Capacity Expansion:
Mayastor does not support the capacity expansion of DiskPools as of v2.9.0.

fsfreeze Operation Failure:
If a pod-based workload is scheduled on a node that reboots and the pod lacks a controller (such as a Deployment or StatefulSet), the volume unpublish operation might not be triggered. This leads the control plane to assume the volume is still published, causing the fsfreeze operation to fail during snapshot creation.

Workaround: Recreate or reinstate the pod to ensure proper volume mounting.

Diskpool's backing device failure
If the backend device that hosts a diskpool runs into a fault, or gets removed e.g cloud disk removal, the status of diskpool and hosted replicas isn't clearly updated to reflect the problem. As a result the resultant failures aren't gracefully handled and volume might remain Degraded for an extended period of time.

Extremely large pool undergoing dirty shutdown
In case of a dirty shutdown of io-engine node hosting an extremely large pool e.g 10TiB or 20TiB, the recovery of pool hangs after the node comes online.

Extremely large filesystem volumes fail to provision
Filesystems volumes of sizes ranging in Terabytes e.g. more than 15TiB fails to provision successfully due to filesystem formatting getting hung.

v4.2.0

Compare Source

Containerized Attached Storage for Kubernetes

v4.1.3

Compare Source

Containerized Attached Storage for Kubernetes

v4.1.2

Compare Source

Containerized Attached Storage for Kubernetes

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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 was generated by Mend Renovate. View the repository job log.