Rook
v1.21.0Storage & DataA breaking release changes Helm chart and Ceph defaults and removes automatic setup for some resources and images. It also adds storage and object-management capabilities, so chart references, kernel compatibility, new NFS installs, and custom CSI image settings may need review.
Check if affected (4)
breakingHelm OCI chart tag format
Applies if you reference Helm OCI chart tags in scripts or tooling.
Helm OCI chart tags no longer include the
vprefix, so1.replaces21. 0 v1.. Scripts and tooling that reference charts by tag need to use the new format.21. 0 breakingCeph
msgrv2default requirementApplies if you cannot use
msgrv2because of an older kernel.Ceph
msgrv2is required by default and requires kernel5.. The11 CephClustersettingnetwork., or the same value underconnections. requireMsgr2: false cephClusterSpecin Helm values, disables the protocol.breakingAutomatic
.pool creationnfs Applies if you are creating a new NFS install.
New NFS installs must define a
CephBlockPoolfor the.pool because Rook no longer creates it automatically. A sample specification is available innfs deploy/examples/nfs.; upgraded clusters are not affected.yaml breakingDefault CSI driver image configuration
Applies if you use custom CSI images.
Rook no longer sets default CSI driver container images. The
rook-csi-operator-image-set-configmapnow has empty values so the ceph-csi-operator uses its built-in defaults; custom image overrides must remain present in the configmap after an upgrade.
All 6 other recorded changesadditions 6
additions (6)
- - RBD Quality of Service (QoS) support is configured via the
VolumeAttributesClassusing the krbd mounter with cgroup v2io.enforcement. See the [RBD QoS documentation](Documentation/Storage-Configuration/Block-Storage-RBD/rbd-qos.md) for details.max - - Automated OSD replacement: An OSD deployment can be annotated to mark it for replacement. Rook will drain and destroy it by preserving its CRUSH position to later reuse it when new device will be available on the same node. All types of OSDs supported for host-based clusters, including OSDs sharing a metadata device. PVC-based OSDs are not supported for this new replacement design. See [OSD replacement design document](./design/ceph/osd-replacement.md) for details.
- - The rook-ceph-cluster Helm chart can create
CephObjectStoreUserresources via the newcephObjectStoreUsersvalue. - - The toolbox deployments from the Helm chart and the example manifests now reload the keyring and
ceph.automatically after CephX key rotation, mon failover, or a config override change.conf - - CephCluster dashboard TLS certificates can now be configured from a same-namespace Kubernetes TLS Secret with
spec.when the dashboard SSL is enabled. Rook reconciles updates to the referenced Secret and restores the default self-signed certificate when the reference is removed.dashboard. sslCertificateRef - -
CephObjectStoreUsergained settingsspec.anddefaultPlacement spec., which set the RGW user's default bucket placement target and default storage class. Both are optional and validated by RGW. The effective values are reported indefaultStorageClass status.. Removing either field stops Rook from managing it and leaves the last applied value in place on the RGW user, except that changinginfo defaultPlacementwithout adefaultStorageClassresets the storage class to the new placement target's default.
A weekly email arrives when a release needs action. Like the breaking changes in this release.