build(deps): bump github.com/rook/rook in /metrics

[dependabot]

Bumps github.com/rook/rook in /metrics from 1.20.0-alpha.0.0.20260707223529-6c2a3a5f2b08 to 1.20.2.

Updates github.com/rook/rook from 1.20.0-alpha.0.0.20260707223529-6c2a3a5f2b08 to 1.20.2

Release notes

Sourced from github.com/rook/rook's releases.

v1.20.2

Improvements

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

• ceph: Update ceph version to latest v20.2.2 (#17774, @​subhamkrai)
• csi: Update ceph-csi-operator version to v1.0.4 (#17875, @​subhamkrai)
• core: Trigger reconcile when node labels or annotations change (#17847, @​anxkhn)
• docs: Add Kubernetes and Ceph version support matrix (#17871, @​jhoblitt)
• core: Add api changes to mute ceph warnings (#17764, @​subhamkrai)
• external: VolumeAttachment should be deleted during unmount (#17826, @​parth-gr)
• core: Ensure config overrides end with a trailing newline (#17758, @​kavirakesh14)
• core: Skip node watcher during initial cache sync (#17812, @​travisn)
• core: Reduce the floating mon reschdule time (#17805, @​parth-gr)
• osd: Do not scan rbd devices in raw activate fallback (#17724, @​jhoblitt)
• security: Restrict mgr NetworkPolicy to ingress-only (#17827, @​OdedViner)
• security: Add example NetworkPolicy CRs for Ceph operand pods (#17559, @​OdedViner)
• object: Generate URL-safe realm access keys (#17710, @​jhoblitt)
• ci: Numerous CI stability updates (@​jhoblitt)

v1.20.1

Improvements

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

• helm: Add rook compatible ceph csi driver values (#17665, @​subhamkrai)
• osd: Ensure require-osd-release set after a major Ceph upgrade (#17546, @​Sunnatillo)
• build: bump golang.org/x/crypto to v0.52.0 (#17718, @​subhamkrai)
• nvmeof: Use Ceph default gateway image when not specified in the nvmeof CR (#17701, @​OdedViner)
• core: Delete stale MDS and RGW pdbs (#17700, @​sp98)
• osd: Support using node labels for OSD device class assignment (#17649, @​yuxiang-he)
• csi: Disable csi-addons by default (#17664, @​subhamkrai)
• object: Clobber bucket policy on modify instead of merging (#17643, @​archy-rock3t-cloud)
• docs: Add an install guide for Two-Node Fenced clusters (#17628, @​parth-gr)
• docs: Add prerequisite to run udev (#17760, @​sp98)
• docs: External cluster documentation updated for the CSI operator (#17690, @​parth-gr)
• docs: Update csi-driver value.yaml reference link (#17674, @​subhamkrai)

v1.20.0

Upgrade Guide

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

Breaking Changes

• The Ceph CSI operator is required for managing CSI driver settings.
  • Upgrades will continue working with the existing settings that had been applied by Rook previously. Further updates to CSI settings will need to be updated by the Rook admin. Clusters with default CSI settings do not require customizations.
  • CSI settings are removed from the Rook operator configmap rook-ceph-operator-config and the rook-ceph Helm chart.
  • New installs must configure the CSI settings with the Ceph-CSI OperatorConfig and Driver CRs. Default settings are included in operator.yaml. For custom CSI settings, see the CSI Configuration for more details and examples.
  • For helm users, the Ceph CSI operator settings are configured by the ceph-csi-drivers chart. Custom CSI images remain configured by the rook-ceph chart values.

Features

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign agarwal-mudit for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a red-hat-storage member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.