2025-08-29 14:36:43 -06:00
|
|
|
# v1.19 Pending Release Notes
|
2020-06-25 09:49:42 +02:00
|
|
|
|
2017-09-14 16:09:23 -07:00
|
|
|
## Breaking Changes
|
2024-02-13 13:30:25 +05:30
|
|
|
|
2026-01-06 13:05:45 -07:00
|
|
|
- The minimum supported Kubernetes version is v1.30.
|
|
|
|
|
|
|
|
|
|
- The minimum supported Ceph version is v19.2.0. Rook v1.18 clusters running Ceph v18 must upgrade
|
|
|
|
|
to Ceph v19.2.0 or higher before upgrading Rook.
|
|
|
|
|
|
2025-11-14 14:40:31 -07:00
|
|
|
- The behavior of the `activeStandby` property in the `CephFilesystem` CRD has changed.
|
2026-01-06 13:05:45 -07:00
|
|
|
When set to `false`, the standby MDS daemon deployment will be scaled down and removed,
|
|
|
|
|
rather than only disabling the standby cache while the daemon remains running.
|
|
|
|
|
|
|
|
|
|
- Helm: The rook-ceph-cluster chart has changed where the Ceph image is defined, to allow separate
|
|
|
|
|
settings for the repository and tag. For more info, see the
|
|
|
|
|
[Rook upgrade guide](https://rook.io/docs/rook/v1.19/Upgrade/rook-upgrade/).
|
|
|
|
|
|
|
|
|
|
- In external mode CephClusters when users give a Ceph admin keyring to Rook, Rook will no longer
|
|
|
|
|
create CSI Ceph clients itself. This makes it so that all external mode clusters are
|
|
|
|
|
managed via the same mechanism (external Python script) and avoids duplicate logic issues.
|
2025-11-14 14:40:31 -07:00
|
|
|
|
2021-07-01 10:57:48 +02:00
|
|
|
## Features
|
2025-11-07 11:58:03 -07:00
|
|
|
|
|
|
|
|
- Experimental: Allow concurrent reconciles of the CephCluster CR when there multiple clusters
|
|
|
|
|
being managed by the same Rook operator. Concurrency is enabled by increasing
|
|
|
|
|
the operator setting `ROOK_RECONCILE_CONCURRENT_CLUSTERS` to a value greater
|
|
|
|
|
than `1`.
|
2025-12-03 10:35:58 -07:00
|
|
|
- Improved logging with namespaced names for the controllers for more consistency in
|
|
|
|
|
troubleshooting the rook operator log.
|
