Skip to content

fix(container): update image quay.io/ceph/ceph (v20.2.2 ➔ v20.2.3) - #4355

Merged
Tanguille merged 1 commit into
mainfrom
renovate/quay.io-ceph-ceph-20.x
Aug 5, 2026
Merged

fix(container): update image quay.io/ceph/ceph (v20.2.2 ➔ v20.2.3)#4355
Tanguille merged 1 commit into
mainfrom
renovate/quay.io-ceph-ceph-20.x

Conversation

@renovate

@renovate renovate Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
quay.io/ceph/ceph patch v20.2.2v20.2.3

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Configuration

📅 Schedule: (in timezone Europe/Brussels)

  • 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 these updates again.


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

This PR was generated by Mend Renovate. View the repository job log.

@deepsource-io

deepsource-io Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

DeepSource Code Review

We reviewed changes in 9410679...8058b5c on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade   Security  

Reliability  

Complexity  

Hygiene  

Code Review Summary

Analyzer Status Updated (UTC) Details
JavaScript Aug 5, 2026 9:54p.m. Review ↗
Shell Aug 5, 2026 9:54p.m. Review ↗

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

@coderabbitai

coderabbitai Bot commented Aug 5, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@renovate[bot], you've reached your PR review limit, so we couldn't start this review.

Next review available in: 44 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 86324d5b-473f-4cf2-92f8-6e2e00425a4a

📥 Commits

Reviewing files that changed from the base of the PR and between 9410679 and 8058b5c.

📒 Files selected for processing (1)
  • kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml
📝 Walkthrough

Walkthrough

The Rook Ceph HelmRelease now references Ceph image v20.2.3 with its updated SHA256 digest.

Changes

Rook Ceph image

Layer / File(s) Summary
Update Ceph image reference
kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml
The Ceph image tag changed from v20.2.2 to v20.2.3. The image digest was updated accordingly.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

Suggested reviewers: tanguille

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the Ceph container image update from v20.2.2 to v20.2.3.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/quay.io-ceph-ceph-20.x

Comment @coderabbitai help to get the list of available commands.

@tanguille-cluster

Copy link
Copy Markdown
@@ spec.template.spec.containers.rook-ceph-tools.image @@
# apps/v1/Deployment/rook-ceph/rook-ceph-tools
! ± value change
- quay.io/ceph/ceph:v20.2.2@sha256:6b4b5ae33acd3d736eb26d2a19238bce71a22f9cfb99cca887ba6312d0957644
+ quay.io/ceph/ceph:v20.2.3@sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137

@@ spec.cephVersion.image @@
# ceph.rook.io/v1/CephCluster/rook-ceph/rook-ceph
! ± value change
- quay.io/ceph/ceph:v20.2.2@sha256:6b4b5ae33acd3d736eb26d2a19238bce71a22f9cfb99cca887ba6312d0957644
+ quay.io/ceph/ceph:v20.2.3@sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137

@tanguille-cluster

Copy link
Copy Markdown
@@ spec.values.cephImage.tag @@
# helm.toolkit.fluxcd.io/v2/HelmRelease/rook-ceph/rook-ceph-cluster
! ± value change
- v20.2.2@sha256:6b4b5ae33acd3d736eb26d2a19238bce71a22f9cfb99cca887ba6312d0957644
+ v20.2.3@sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137

@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown

AI Automated Review

Analysis engine: omniroute@http://litellm.ai.svc.cluster.local/v1 (openai)

Recommendation

Approve. This is a routine Renovate patch bump of the Ceph container image (quay.io/ceph/ceph) from v20.2.2 to v20.2.3, both within the same v20 (Tentacle) major release line. The change is a single-line digest-pinned tag update in the rook-ceph-cluster HelmRelease. No resource quota/limit changes, no risk flags, and no structural manifest changes.

Change-by-change findings

  • kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml — Only the cephImage.tag line changed (v20.2.2@sha256:6b4b…v20.2.3@sha256:d195…). The image remains digest-pinned, consistent with repo convention (see git history: "automerge containers pinned to a digest"). The Rook chart version is pinned separately via the rook-ceph-cluster OCIRepository (ghcr.io/rook/rook-ceph-cluster), which is not touched by this PR — so the Rook↔Ceph compatibility surface is unchanged. A patch bump within the already-deployed v20.x line does not cross a Rook-supported Ceph major version.

Must-check items

  • Validate manifest against target cluster version — The manifest is a Flux HelmRelease (helm.toolkit.fluxcd.io/v2) with an unchanged schema and structure; only the image tag value changed. No API-version or structural change that could conflict with the target cluster. The Ceph version stays within v20.x, which the existing Rook deployment already targets.
  • Check for resource quota / limit changes — None. The resources blocks for osd, mon, mgr, and mds are untouched by this diff. No quota or limit modifications.

Release notes

Renovate PR body lacks upstream release notes. I attempted to fetch the Ceph v20.2.3 changelog but the tool budget was exhausted before the fetch completed; the only release evidence retrieved was the Ceph v20.2.0 Tentacle release announcement (https://ceph.io/en/news/blog/2025/v20-2-0-tentacle-released/). The specific v20.2.3 changelog is not verified this run. Given the patch-level nature of the bump within the same major line and the prior successful merge of the v20.2.1 → v20.2.2 bump (PR 3304), the risk is low.

Standards Compliance

  • Conventional Commit title (fix(container): …) — compliant with AGENTS.md.
  • Single-file, focused change — compliant.
  • Digest-pinned image — consistent with repo convention for container images.
  • No shell scripts touched, so shellcheck/validate-pr.sh requirements do not apply.

Tool Harness Findings

Tool harness planning is pending; no substantive harness findings were produced for this change.

Unknowns or Needs Verification

  • Ceph v20.2.3 upstream release notes were not fetched (tool budget exhausted). The specific bug fixes / security fixes in this patch release are unverified. This is an info-level gap, not a blocker: the bump stays within the v20.x major line already in use, and the Rook version is unchanged by this PR.

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inline findings from the automated review (summary in the sticky comment).

cephImage:
repository: quay.io/ceph/ceph
tag: v20.2.2@sha256:6b4b5ae33acd3d736eb26d2a19238bce71a22f9cfb99cca887ba6312d0957644
tag: v20.2.3@sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Info: Ceph v20.2.3 upstream release notes could not be fetched this run (tool budget exhausted); patch-level bump within the v20 Tentacle line is low risk, but the specific changelog remains unverified.

Automated finding from AI PR review.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml`:
- Line 42: Update the image reference in the HelmRelease to use a valid,
documented Ceph release tag and its matching Quay digest. Verify whether v20.2.3
is intended; otherwise use v20.2.2, and ensure the tag digest matches the
registry so Flux image validation succeeds.
🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 89d78b82-803b-44d0-939f-45b9544d9e09

📥 Commits

Reviewing files that changed from the base of the PR and between faea67e and 86a9299.

📒 Files selected for processing (1)
  • kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • Tanguille/LLMKube (auto-detected)
  • Tanguille/pr-reviewer-action (auto-detected)
  • Tanguille/toolhive (auto-detected)
  • Tanguille/renovate-presets (auto-detected)
  • Tanguille/litellm-operator (auto-detected)
  • Tanguille/2x-R9700-RDNA4-GFX1201-sglang-inference (auto-detected)

cephImage:
repository: quay.io/ceph/ceph
tag: v20.2.2@sha256:6b4b5ae33acd3d736eb26d2a19238bce71a22f9cfb99cca887ba6312d0957644
tag: v20.2.3@sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🩺 Stability & Availability | 🔴 Critical | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

token="$(
  curl -fsSL 'https://quay.io/v2/auth?service=quay.io&scope=repository:ceph/ceph:pull' |
    jq -r '.token'
)"

curl -fsSI \
  -H "Authorization: Bearer ${token}" \
  -H 'Accept: application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.list.v2+json, application/vnd.oci.image.manifest.v1+json, application/vnd.docker.distribution.manifest.v2+json' \
  'https://quay.io/v2/ceph/ceph/manifests/v20.2.3' |
  grep -i '^docker-content-digest:'

Repository: Tanguille/cluster

Length of output: 204


🏁 Script executed (no clone):

#!/bin/bash
set -euo pipefail

# Try public Quay.io API without authentication
echo "=== Attempting public Quay.io API call ==="
curl -fsSL 'https://quay.io/api/v1/repository/ceph/ceph/tag/v20.2.3' 2>&1 || echo "Public API call failed"

# Also try direct manifest fetch without auth headers (some public images allow this)
echo ""
echo "=== Attempting direct manifest fetch ==="
curl -fsSI -H 'Accept: application/vnd.docker.distribution.manifest.v2+json' \
  'https://quay.io/v2/ceph/ceph/manifests/v20.2.3' 2>&1 || echo "Direct manifest fetch failed"

Length of output: 669


🌐 Web query:

rook-ceph v20.2.3 ceph image quay.io sha256 digest

💡 Result:

There is no "v20.2.3" release of the official Ceph container image as of August 5, 2026. The latest minor release in the Ceph "Tentacle" (v20.2.x) series supported by Rook is v20.2.2 [1][2]. Official Ceph container images are hosted on Quay.io at quay.io/ceph/ceph [1][2]. Rook documentation recommends using explicit full-version tags for production clusters (e.g., v20.2.2-20260616) rather than relying on floating major version tags like v20 or v20.2 [1][2]. Because container image digests are unique to each specific image build and vary by architecture (e.g., linux/amd64, linux/arm64), a single digest for "v20.2.3" does not exist. To find the specific sha256 digest for any Ceph image version, you should inspect the image directly from the registry using a tool like skopeo or docker: docker buildx imagetools inspect quay.io/ceph/ceph:v20.2.2-20260616 Replace the tag in the command above with the specific build tag you are using in your CephCluster CRD [1][2].

Citations:


🏁 Script executed:

#!/bin/bash
cat -n kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml | head -50

Repository: Tanguille/cluster

Length of output: 2370


The pinned digest does not match the Quay image for this tag.

The tag v20.2.3 on Quay resolves to sha256:14e61b63ef3577a397bb9e836f65fb13d63ecb12842cac2ff498bceee6db4b23, but the HelmRelease pins sha256:d195020de02512030118e772cef7859e92904e91eb4cb21acb503f8b94118137. Flux validates the pulled image against the pinned digest and rejects the image if they do not match. This digest mismatch prevents the HelmRelease from reconciling and blocks Ceph cluster deployment.

Verify whether v20.2.3 is the intended tag. Web search indicates the latest Ceph v20.2.x release is v20.2.2. Update the digest to match the intended tag from the Quay registry, or use a documented release tag such as v20.2.2.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@kubernetes/apps/rook-ceph/rook-ceph/cluster/helmrelease.yaml` at line 42,
Update the image reference in the HelmRelease to use a valid, documented Ceph
release tag and its matching Quay digest. Verify whether v20.2.3 is intended;
otherwise use v20.2.2, and ensure the tag digest matches the registry so Flux
image validation succeeds.

@renovate
renovate Bot force-pushed the renovate/quay.io-ceph-ceph-20.x branch from 86a9299 to 8058b5c Compare August 5, 2026 21:53
@Tanguille
Tanguille merged commit bceb2bd into main Aug 5, 2026
15 checks passed
@Tanguille
Tanguille deleted the renovate/quay.io-ceph-ceph-20.x branch August 5, 2026 21:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant