forked from rook/rook
Sébastien Han
d3845e7f75
This requirement is long gone and was reported in 2017. Clients should have been updated by then, so there is no reason to set the CRUSH tunable to such an old client. Actually, we should let Ceph run its own tunable. They can always be changed later. Also, this was really restrictive and applied on every orchestration and thus would override any other config done by an administrator. Even worse, this will trigger data movement back and forth... Closes: https://github.com/rook/rook/issues/3138 Signed-off-by: Sébastien Han <seb@redhat.com>
1.9 KiB
1.9 KiB
Major Themes
Action Required
Notable Features
- Creation of storage pools through the custom resource definitions (CRDs) now allows users to optionally specify
deviceClassproperty to enable distribution of the data only across the specified device class. See Ceph Block Pool CRD for an example usage
Ceph
- Rook can now be configured to read "region" and "zone" labels on Kubernetes nodes and use that information as part of the CRUSH location for the OSDs.
- Rgw pods have liveness probe enabled
- Rgw is now configured with the Beast backend as of the Nautilus release
- OSD: newly updated cluster from 0.9 to 1.0.3 and thus Ceph Nautilus will have their OSDs allowing new features for Nautilus
- Rgw instances have their own key and thus are properly reflected in the Ceph status
- The Rook Agent pods are now started when the CephCluster is created rather than immediately when the operator is started.
- Ceph CRUSH tunable are not enforced to "firefly" anymore, Ceph picks the right tunable for its own version, to read more about tunable see the Ceph documentation
Breaking Changes
Known Issues
Deprecations
Ceph
- For rgw, when deploying an object store with
object.yaml, usingallNodesis not supported anymore, a transition path has been implemented in the code though. So if you were usingallNodes: true, Rook will replace each daemonset with a deployment (one for one replacement) gradually. This operation will be triggered on an update or when a new version of the operator is deployed. Once complete, it is expected that you edit your object CR withkubectl -n rook-ceph edit cephobjectstore.ceph.rook.io/my-storeand setallNodes: falseandinstanceswith the current number of rgw instances.