Files
my-rook-config/PendingReleaseNotes.md
T

19 lines
2.0 KiB
Markdown
Raw Normal View History

2026-01-21 15:46:36 -07:00
# v1.20 Pending Release Notes
2020-06-25 09:49:42 +02:00
2017-09-14 16:09:23 -07:00
## Breaking Changes
2026-01-21 15:46:36 -07:00
- The minimum supported Kubernetes version is v1.31.
2026-03-10 15:41:57 +05:30
- The CSI operator is required for managing CSI driver settings.
- The CSI settings are removed from the Rook operator configmap and helm chart
- New installs must configure the CSI settings with the CSI CRs instead of Rook operator settings.
- Upgrades will continue working with the existing settings that had been applied by Rook previously. Further updates to CSI settings will need to be updated by the Rook admin.
## Features
2026-04-06 12:18:47 +05:30
- The latest supported Kubernetes version is v1.36.
2026-04-06 12:18:47 +05:30
- RGW Account support: Added `CephObjectStoreAccount` CRD for managing RGW accounts, and `accountRef` field in `CephObjectStoreUser` to associate users with accounts. This feature is experimental and currently only supported with the Ceph main branch image (`quay.ceph.io/ceph-ci/ceph:main`). See the [Object Store Accounts](Documentation/Storage-Configuration/Object-Storage-RGW/ceph-object-accounts.md) documentation for more details.
2026-04-02 21:56:21 +05:30
- SSE-S3 with Vault Agent: Added support for server-side encryption with SSE-S3 using HashiCorp Vault Agent authentication. See the [CephObjectStore Security Settings](Documentation/CRDs/Object-Storage/ceph-object-store-crd.md#sse-s3-with-vault-agent) for more details.
2026-04-24 23:57:27 +05:30
- Unused CRUSH rule cleanup: Rook now deletes unused CRUSH rules by default after the Ceph mgr starts. Set `ROOK_DELETE_UNUSED_CRUSH_RULES` to `false` in the operator config to disable this cleanup.
- Declare stable the feature to concurrently reconcile multiple Ceph Clusters with the setting `ROOK_RECONCILE_CONCURRENT_CLUSTERS`.
- Containers within a pod are now consistently reconciled by name instead of relying on the order in which they are declared. This is a defensive measure against the declaration order changing due to manipulation by a mutating webhook.
- OSD resize with encrypted host-based OSDs: When using `encryptedDevice: true` with host-based (non-PVC) OSDs, resizing the underlying disk now automatically expands encrypted OSDs.