alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 5 Actions Activity

Update Helm release rook-ceph-cluster to v1.17.0 #147

Merged
alexlebens merged 1 commits from renovate/rook-ceph-cluster-1.x into main 2025-04-17 20:41:47 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2025-04-17 20:00:52 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
rook-ceph-cluster minor v1.16.6 -> v1.17.0

Release Notes

rook/rook (rook-ceph-cluster)

v1.17.0

Compare Source

Upgrade Guide

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

Breaking Changes

  • Kubernetes v1.28 is now the minimum version supported by Rook through the soon-to-be K8s release v1.33.
  • Several ObjectBucketClaim options were added previously in Rook v1.16 that allowed more control over buckets. These controls allow users to self-serve their own S3 policies. Administrators may consider this flexibility a risk, depending on their environment. Rook now disables these options by default to ensure the safest off-the-shelf configurations. To enable the full range of OBC configurations, the new setting ROOK_OBC_ALLOW_ADDITIONAL_CONFIG_FIELDS must be set to enable users to set all of these options. For more details, see the OBC additionalConfig documentation.
  • First-class credential management added to CephObjectStoreUser resources, allowing multiple credentials and declarative credential rotation. For more details, see Managing User S3 Credentials. As a result, existing S3 users provisioned via CephObjectStoreUser resources no longer allow multiple credentials to exist on underlying S3 users, unless explicitly managed by Rook. Rook will purge all but one of the undeclared credentials. This could be a user observable regression for administrators who manually edited/rotated S3 user credentials for CephObjectStoreUsers, and affected users can make use of the new credential management feature as an alternative.
  • Kafka notifications configured via CephBucketTopic resources will now default to setting the Kafka authentication mechanism to PLAIN. Previously, no auth mechanism was specified by default. It was possible to set the auth mechanism via CephBucketTopic.spec.endpoint.kafka.opaqueData. However, setting &mechanism=<auth type> via opaqueData is no longer possible. If any auth mechanism other than PLAIN is in use, modification to CephBucketTopic resources is required.

Features

  • The name of a pre-existing Ceph RGW user account can be set as the bucket owner on an ObjectBucketClaim (OBC), rather than a unique RGW user being created for every bucket. A CephObjectStoreUser resource may be used to create the Ceph RGW user account which will be specified on the OBC. If the bucket owner is set on a bucket that already exists and is owned by a different user, the bucket will be re-linked to the specified user.
  • The Ceph CSI 3.14 release has a number of features and improvements for RBD and CephFS volumes, volume snapshots, and many more areas. See the Ceph CSI 3.14 release notes for more details.
  • External mons: In some two-datacenter clusters, there is no option to start an arbiter mon in an independent K8s node to configure a proper stretch cluster. The external mons now allow a mon to be configured outside the Kubernetes cluster, while Rook manages everything else inside the cluster. For more details, see the External Mon documentation. This feature is in currently in experimental mode.
  • DNS resolution for mons: Allows clients outside the K8s cluster to resolve mon endpoints via DNS without requiring manual updates to the list of mon endpoints. This helps in scenarios such as virtual machine live migration. The Ceph client can connect to rook-ceph-active-mons..svc.cluster.local to dynamically resolve mon endpoints and receive automatic updates when mon IPs change. To configure this DNS resolution, see Tracking Mon Endpoints.
  • Node-specific ceph.conf overrides: The ceph.conf overrides can now be customized per-node. This may be helpful for some ceph.conf settings that need to be unique per node depending on the hardware. This can be configured by creating a node-specific configmap that will be loaded for all OSDs and OSD prepare jobs on that node, instead of the default settings that are loaded from the rook-config-override configmap.

v1.16.7

Compare Source

Improvements

Rook v1.16.7 is a patch release limited in scope and focusing on feature additions and bug fixes to the Ceph operator.

Configuration

📅 Schedule: Branch creation - "* */1 * * *" in timezone US/Central, Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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-cluster](https://github.com/rook/rook) | minor | `v1.16.6` -> `v1.17.0` | --- ### Release Notes <details> <summary>rook/rook (rook-ceph-cluster)</summary> ### [`v1.17.0`](https://github.com/rook/rook/releases/tag/v1.17.0) [Compare Source](https://github.com/rook/rook/compare/v1.16.7...v1.17.0) #### Upgrade Guide To upgrade from previous versions of Rook, see the [Rook upgrade guide](https://rook.github.io/docs/rook/v1.17/Upgrade/rook-upgrade/). #### Breaking Changes - Kubernetes v1.28 is now the minimum version supported by Rook through the soon-to-be K8s release v1.33. - Several ObjectBucketClaim options were added previously in Rook v1.16 that allowed more control over buckets. These controls allow users to self-serve their own S3 policies. Administrators may consider this flexibility a risk, depending on their environment. Rook now disables these options by default to ensure the safest off-the-shelf configurations. To enable the full range of OBC configurations, the new setting `ROOK_OBC_ALLOW_ADDITIONAL_CONFIG_FIELDS` must be set to enable users to set all of these options. For more details, see the [OBC additionalConfig documentation](https://rook.io/docs/rook/v1.17/Storage-Configuration/Object-Storage-RGW/ceph-object-bucket-claim/#obc-custom-resource). - First-class credential management added to CephObjectStoreUser resources, allowing multiple credentials and declarative credential rotation. For more details, see [Managing User S3 Credentials](https://rook.io/docs/rook/v1.17/Storage-Configuration/Object-Storage-RGW/object-storage/#managing-user-s3-credentials). As a result, existing S3 users provisioned via CephObjectStoreUser resources no longer allow multiple credentials to exist on underlying S3 users, unless explicitly managed by Rook. Rook will purge all but one of the undeclared credentials. This could be a user observable regression for administrators who manually edited/rotated S3 user credentials for CephObjectStoreUsers, and affected users can make use of the new credential management feature as an alternative. - Kafka notifications configured via CephBucketTopic resources will now default to setting the Kafka authentication mechanism to `PLAIN`. Previously, no auth mechanism was specified by default. It was possible to set the auth mechanism via `CephBucketTopic.spec.endpoint.kafka.opaqueData`. However, setting `&mechanism=<auth type>` via `opaqueData` is no longer possible. If any auth mechanism other than `PLAIN` is in use, modification to `CephBucketTopic` resources is required. #### Features - The name of a pre-existing Ceph RGW user account can be set as the bucket owner on an ObjectBucketClaim (OBC), rather than a unique RGW user being created for every bucket. A CephObjectStoreUser resource may be used to create the Ceph RGW user account which will be specified on the OBC. If the bucket owner is set on a bucket that already exists and is owned by a different user, the bucket will be re-linked to the specified user. - The Ceph CSI 3.14 release has a number of features and improvements for RBD and CephFS volumes, volume snapshots, and many more areas. See the [Ceph CSI 3.14 release notes](https://github.com/ceph/ceph-csi/releases/tag/v3.14.0) for more details. - External mons: In some two-datacenter clusters, there is no option to start an arbiter mon in an independent K8s node to configure a proper [stretch cluster](https://rook.io/docs/rook/v1.17/CRDs/Cluster/stretch-cluster/). The external mons now allow a mon to be configured outside the Kubernetes cluster, while Rook manages everything else inside the cluster. For more details, see the [External Mon documentation](https://rook.io/docs/rook/v1.17/Storage-Configuration/Advanced/ceph-mon-health/#external-monitors). This feature is in currently in experimental mode. - DNS resolution for mons: Allows clients outside the K8s cluster to resolve mon endpoints via DNS without requiring manual updates to the list of mon endpoints. This helps in scenarios such as virtual machine live migration. The Ceph client can connect to rook-ceph-active-mons.<namespace>.svc.cluster.local to dynamically resolve mon endpoints and receive automatic updates when mon IPs change. To configure this DNS resolution, see [Tracking Mon Endpoints](https://rook.io/docs/rook/v1.17/Storage-Configuration/Advanced/ceph-mon-health/#tracking-mon-endpoints). - Node-specific ceph.conf overrides: The [ceph.conf overrides](https://rook.io/docs/rook/latest-release/Storage-Configuration/Advanced/ceph-configuration/#custom-cephconf-settings) can now be customized per-node. This may be helpful for some ceph.conf settings that need to be unique per node depending on the hardware. This can be configured by creating a node-specific configmap that will be loaded for all OSDs and OSD prepare jobs on that node, instead of the default settings that are loaded from the rook-config-override configmap. ### [`v1.16.7`](https://github.com/rook/rook/releases/tag/v1.16.7) [Compare Source](https://github.com/rook/rook/compare/v1.16.6...v1.16.7) ### Improvements Rook v1.16.7 is a patch release limited in scope and focusing on feature additions and bug fixes to the Ceph operator. - core: Set default Ceph version to v19.2.2 ([#&#8203;15704](https://github.com/rook/rook/issues/15704), [@&#8203;travisn](https://github.com/travisn)) - mon: Ensure mon canary pods are cleaned up for multicluster service ([#&#8203;15718](https://github.com/rook/rook/issues/15718), [@&#8203;sp98](https://github.com/sp98)) - core: Print correct OSD ID in key rotation logs ([#&#8203;15727](https://github.com/rook/rook/issues/15727), [@&#8203;sp98](https://github.com/sp98)) - helm: Add labels to ingress resource ([#&#8203;15719](https://github.com/rook/rook/issues/15719), [@&#8203;chkpwd](https://github.com/chkpwd)) - core: Update cephstatus fsmap gid type to uint64 ([#&#8203;15690](https://github.com/rook/rook/issues/15690), [@&#8203;BlaineEXE](https://github.com/BlaineEXE)) - pool: Retry status update on fail ([#&#8203;15593](https://github.com/rook/rook/issues/15593), [@&#8203;prazumovsky](https://github.com/prazumovsky)) - helm: Allow specifying an ingress object store port to override default ([#&#8203;15669](https://github.com/rook/rook/issues/15669), [@&#8203;travisn](https://github.com/travisn)) - rbdmirror: Fix the rados namespace health checkup ([#&#8203;15677](https://github.com/rook/rook/issues/15677), [@&#8203;parth-gr](https://github.com/parth-gr)) - osd: Stabilize oscillating maxUnavailable in pdbs in case of node drain ([#&#8203;15634](https://github.com/rook/rook/issues/15634), [@&#8203;sp98](https://github.com/sp98)) - ci: Update x/net version to fix snyk report ([#&#8203;15659](https://github.com/rook/rook/issues/15659), [@&#8203;subhamkrai](https://github.com/subhamkrai)) - nfs: Set allow_set_io_flusher_fail=true in config ([#&#8203;15652](https://github.com/rook/rook/issues/15652), [@&#8203;BlaineEXE](https://github.com/BlaineEXE)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "* */1 * * *" in timezone US/Central, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMTAuMCIsInVwZGF0ZWRJblZlciI6IjM5LjIxMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJjaGFydCJdfQ==-->
renovate-bot added 1 commit 2025-04-17 20:00:53 +00:00
Update Helm release rook-ceph-cluster to v1.17.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
lint-and-test-charts / lint-test (pull_request) Successful in 33s
Details
cc1abcdd7a
alexlebens merged commit 412fddc02a into main 2025-04-17 20:41:47 +00:00
alexlebens deleted branch renovate/rook-ceph-cluster-1.x 2025-04-17 20:41:47 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
automerge
This PR will be automerged by Renovate.
chart
Chart update generated by Renovate.
image
Image update generated by Renovate.
stale
PR or Issue that has not been updated recently.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#147
No description provided.
Delete Branch "renovate/rook-ceph-cluster-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?