发布日期: 2025-08-20
版本号: v1.18.0

Rook升级指南建议参考官方文档。本次升级要求Kubernetes最低版本为v1.29（支持至v1.34），并支持Helm v3.13及以上版本。新特性包括：Ceph CSI操作器现已成为默认组件，用于管理RBD、CephFS和NFS的CSI驱动；集成Ceph CSI v3.15版本；实验性支持CephX密钥轮换功能；允许在CephBlockPoolRadosNamespace和CephFilesystemSubVolumeGroup资源中指定clusterID；优化了监控器故障转移逻辑，当原节点不存在时将立即切换。此外，Rook将在Ceph Tentacle v20发布后提供支持。

更新内容 （中文）

升级指南

要从Rook的早期版本升级，请参阅 Rook升级指南。

重大变更

  • Rook现在支持的Kubernetes最低版本为v1.29，并将持续支持到即将发布的K8s v1.34。
  • 现在支持Helm 3.13及更高版本。此前，仅测试了最新版Helm，文档也只将Helm 3.x列为前提条件。现在Rook支持Helm最近的六个次版本及其补丁更新。
  • Rook现在在CephCluster创建期间验证节点拓扑，以防止OSD的CRUSH层级结构配置错误。如果像topology.rook.io/rack这样的子标签在区域间重复，集群创建将失败。此检查仅适用于没有OSD的新集群。对于已有OSD的集群，只会记录警告并继续运行。如果您的拓扑结构中检查无效，可以通过在rook-ceph-operator-config配置映射中设置ROOK_SKIP_OSD_TOPOLOGY_CHECK=true来禁用检查。

功能特性

  • Ceph CSI operator现在是配置RBD、CephFS和NFS卷的CSI驱动的默认且推荐组件。CSI operator已从Rook中分离出来，独立运行以管理Ceph-CSI驱动。
    • 在升级过程中以及整个v1.18.x版本期间，Rook会自动将任何Rook CSI设置转换为新的CSI operator CR。此转换预计是完全透明的。在未来v1.19版本中，Rook将放弃对这些设置的直接控制，以便高级用户在配置CSI驱动时能有更多灵活性。届时，我们将提供直接配置这些新Ceph CSI operator CR的指南。
    • 安装时，如快速入门指南中所述，需要创建一个新的清单文件：csi-operator.yaml。
    • 如果使用Helm chart安装，Ceph CSI operator将通过rook-ceph chart中的新Helm设置csi.rookUseCsiOperator默认自动安装。
    • 如果发现阻塞性问题，可以通过在operator.yaml中设置ROOK_USE_CSI_OPERATOR: false或应用Helm设置csi.rookUseCsiOperator: false来重新启用之前的CSI驱动。
  • Ceph CSI v3.15 为RBD、CephFS和NFS驱动带来了一系列功能和改进。此版本既受Ceph CSI operator支持，也受Rook的直接配置模式支持。从下一个版本（年底）开始，将必须使用Ceph CSI operator来配置CSI驱动。
  • CephX密钥轮换 现已作为实验性功能提供，用于Ceph守护进程和客户端使用的CephX认证密钥。用户将在新部署的Rook集群中的部分Rook资源上看到新的CephX状态项。用户还可以找到spec.security.cephx设置，这些设置允许为不同的Ceph组件启动CephX密钥轮换。密钥轮换的完整文档可在此处找到。
    • 密钥轮换需要Ceph版本v19.2.3或更高版本。
    • Ceph admin和mon密钥尚不能轮换。在实验模式下，实现仍在进行中。
  • 增加对在CephBlockPoolRadosNamespace和CephFilesystemSubVolumeGroup CR中指定clusterID的支持。
  • 当一个mon正在故障切换时，如果指定的节点不再存在，该mon将立即进行故障切换，而不是等待20分钟超时。
  • 对Ceph Tentacle v20的支持将在其发布后立即提供。

更新内容 （原始）

Upgrade Guide

To upgrade from previous versions of Rook, see the Rook upgrade guide.

Breaking Changes

  • Kubernetes v1.29 is now the minimum version supported by Rook through the soon-to-be K8s release v1.34.
  • Helm versions 3.13 and newer are supported. Previously, only the latest version of helm was tested and the docs stated only version 3.x of helm as a prerequisite. Now rook supports the six most recent minor versions of helm along with their their patch updates.
  • Rook now validates node topology during CephCluster creation to prevent misconfigured CRUSH hierarchies for OSDs. If child labels like topology.rook.io/rack are duplicated across zones, cluster creation will fail. The check applies only to new clusters without OSDs. Clusters with existing OSDs will only log a warning and continue. If the checks are invalid in your topology, they can be suppressed by setting ROOK_SKIP_OSD_TOPOLOGY_CHECK=true in the rook-ceph-operator-config configmap.

Features

  • The Ceph CSI operator is now the default and recommended component for configuring CSI drivers for RBD, CephFS, and NFS volumes. The CSI operator has been factored out of Rook to run independently to manage the Ceph-CSI driver. 
    • During the upgrade and throughout the v1.18.x releases, Rook will automatically convert any Rook CSI settings to the new CSI operator CRs. This transition is expected to be completely transparent. In the future v1.19 release, Rook will relinquish direct control of these settings so advanced users can have more flexibility when configuring the CSI drivers. At that time, we will have a guide on configuring these new Ceph CSI operator CRs directly.
    • During install, as mentioned in the Quickstart Guide, there is a new manifest to be created: csi-operator.yaml
    • If installing with the helm chart, the Ceph CSI operator will automatically be installed by default with the new helm setting csi.rookUseCsiOperator in the rook-ceph chart.
    • If a blocking issue is found, the previous CSI driver can be re-enabled by setting ROOK_USE_CSI_OPERATOR: false in operator.yaml or by applying the helm setting csi.rookUseCsiOperator: false.
  • Ceph CSI v3.15 has a range of features and improvements for the RBD, CephFS, and NFS drivers. This release is supported both by the Ceph CSI operator and Rook’s direct mode of configuration. Starting in the next release (at the end of the year), the Ceph CSI operator will be required to configure the CSI driver.
  • CephX key rotation is now available as an experimental feature for the CephX authentication keys used by Ceph daemons and clients. Users will begin to see new cephx status items on some Rook resources in newly-deployed Rook clusters. Users can also find spec.security.cephx settings that allow initiating CephX key rotation for various Ceph components. Full documentation for key rotation can be found here.
    • Ceph version v19.2.3+ is required for key rotation.
    • The Ceph admin and mon keys cannot yet be rotated. Implementation is still in progress while in experimental mode.
  • Add support for specifying the clusterID in the CephBlockPoolRadosNamespace and the CephFilesystemSubVolumeGroup CR.
  • When a mon is being failed over, if the assigned node no longer exists, the mon is failed over immediately instead of waiting for a 20 minute timeout.
  • Support for Ceph Tentacle v20 will be available as soon as it is released.

下载链接