infrastructure/weyma-talos
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

chore(deps): update helm release rook-ceph to v1.19.0 #198

Merged
williamp merged 1 commits from renovate/rook-ceph-1.x into main 2026-01-21 00:54:56 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2026-01-20 20:01:09 +00:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
rook-ceph minor v1.18.9 -> v1.19.0

Release Notes

rook/rook (rook-ceph)

v1.19.0

Compare Source

Upgrade Guide

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

Breaking Changes

  • The supported Kubernetes versions are v1.30 - v1.35
  • 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.
  • The behavior of the activeStandby property in the CephFilesystem CRD has changed. 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 details, see the Rook upgrade guide.
  • In external mode, when users provide a Ceph admin keyring to Rook, Rook will no longer create CSI Ceph clients automatically. This approach will provide more consistency to configure external mode clusters via the same external Python script.

Features

  • Experimental: NVMe over Fabrics (NVMe-oF) allows RBD volumes to be exposed and accessed via the NVMe/TCP protocol. This enables both Kubernetes pods within the cluster and external clients outside the cluster to connect to Ceph block storage using standard NVMe-oF initiators, providing high-performance block storage access over the network. See the NVMe-oF Configuration Guide to get started.
  • CephCSI v3.16 Integration:
    • NVMe-oF CSI driver for provisioning and mounting volumes over the NVMe over Fabrics protocol
    • Improved fencing for RBD and CephFS volumes during node failure
    • Block volume usage statistics
    • Configurable block encryption cipher
  • 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.
  • Improved logging with namespaced names for the controllers for more consistency in troubleshooting the rook operator log.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [rook-ceph](https://github.com/rook/rook) | minor | `v1.18.9` -> `v1.19.0` | --- ### Release Notes <details> <summary>rook/rook (rook-ceph)</summary> ### [`v1.19.0`](https://github.com/rook/rook/releases/tag/v1.19.0) [Compare Source](https://github.com/rook/rook/compare/v1.18.9...v1.19.0) ### Upgrade Guide To upgrade from previous versions of Rook, see the [Rook upgrade guide](https://rook.github.io/docs/rook/v1.19/Upgrade/rook-upgrade/). ### Breaking Changes - The supported Kubernetes versions are v1.30 - v1.35 - 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. - The behavior of the `activeStandby` property in the `CephFilesystem` CRD has changed. 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 details, see the [Rook upgrade guide](https://rook.io/docs/rook/v1.19/Upgrade/rook-upgrade/#breaking-changes-in-v119). - In external mode, when users provide a Ceph admin keyring to Rook, Rook will no longer create CSI Ceph clients automatically. This approach will provide more consistency to configure external mode clusters via the same external Python script. ### Features - Experimental: NVMe over Fabrics (NVMe-oF) allows RBD volumes to be exposed and accessed via the NVMe/TCP protocol. This enables both Kubernetes pods within the cluster and external clients outside the cluster to connect to Ceph block storage using standard NVMe-oF initiators, providing high-performance block storage access over the network. See the [NVMe-oF Configuration Guide](https://rook.io/docs/rook/latest-release/Storage-Configuration/Block-Storage-RBD/nvme-of/) to get started. - CephCSI v3.16 Integration: - NVMe-oF CSI driver for provisioning and mounting volumes over the NVMe over Fabrics protocol - Improved fencing for RBD and CephFS volumes during [node failure](https://rook.io/docs/rook/latest-release/Storage-Configuration/Block-Storage-RBD/block-storage/#node-loss) - Block volume usage statistics - Configurable block encryption cipher - 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`. - Improved logging with namespaced names for the controllers for more consistency in troubleshooting the rook operator log. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MC4xNC42IiwidXBkYXRlZEluVmVyIjoiNDAuMTQuNiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
renovate-bot added 1 commit 2026-01-20 20:01:09 +00:00
chore(deps): update helm release rook-ceph to v1.19.0 f1fd7c6cb1
williamp merged commit 6e22223c4b into main 2026-01-21 00:54:56 +00:00
williamp deleted branch renovate/rook-ceph-1.x 2026-01-21 00:54:56 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
actions renovate-bot williamp
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: infrastructure/weyma-talos#198
Delete Branch "renovate/rook-ceph-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?