Bundle Update from Snapshot crt-nshift-lightspeed-tenant/ols-20260618-123847-000

[raptorsun]

This PR is triggered by the release crt-nshift-lightspeed-tenant/ols-20260618-123847-000-8c0481b-xlbbx.

Summary by CodeRabbit

• Chores
  • Refreshed the Lightspeed Operator ClusterServiceVersion to use updated image digests for the service, console plugin variants, and OCP RAG components.
  • Updated the operator manifest metadata timestamp and ensured the related image references in status reflect the same digest updates.

[coderabbitai]

Warning

Review limit reached

@raptorsun, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 3 minutes and 35 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: bd496c5f-4c34-4f5c-b7b8-f0b21c206bc7

📥 Commits

Reviewing files that changed from the base of the PR and between 8d6027e and 807a324.

⛔ Files ignored due to path filters (1)

• related_images.json is excluded by !related_images.json

📒 Files selected for processing (1)

• bundle/manifests/lightspeed-operator.clusterserviceversion.yaml

📝 Walkthrough

Walkthrough

The bundle/manifests/lightspeed-operator.clusterserviceversion.yaml ClusterServiceVersion manifest is updated with a new metadata.annotations.createdAt timestamp and refreshed image digests for the lightspeed-service-api, lightspeed-console-plugin, and lightspeed-ocp-rag components. The controller-manager container's --service-image, --console-image, and --ocp-rag-image arguments are updated, and the corresponding relatedImages entries are synchronized to match.

Changes

ClusterServiceVersion Manifest Updates

Layer / File(s)	Summary
Metadata timestamp update bundle/manifests/lightspeed-operator.clusterserviceversion.yaml	Updates the metadata.annotations.createdAt annotation value.
Image digest synchronization bundle/manifests/lightspeed-operator.clusterserviceversion.yaml	Updates the controller-manager container --service-image, --console-image, and --ocp-rag-image argument digests, and synchronizes the corresponding relatedImages entries for lightspeed-service-api, lightspeed-console-plugin, lightspeed-console-plugin-pf5, and lightspeed-ocp-rag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• openshift/lightspeed-operator#1691: Both PRs update the same bundle/manifests/lightspeed-operator.clusterserviceversion.yaml by changing the controller-manager image digest args (service/console/RAG) and the corresponding status.relatedImages digests.
• openshift/lightspeed-operator#1710: Both PRs update the same bundle/manifests/lightspeed-operator.clusterserviceversion.yaml by bumping metadata.annotations.createdAt and changing the container/status.relatedImages image digests for Lightspeed components (e.g., console-plugin-pf5 and ocp-rag).
• openshift/lightspeed-operator#1716: Both PRs update bundle/manifests/lightspeed-operator.clusterserviceversion.yaml by changing the same manager container image/digest references and corresponding status.relatedImages entries for the Lightspeed console-plugin and related components.

Suggested reviewers

• bparees
• xrajesh

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: a bundle update from a specific snapshot release.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[red-hat-konflux]

label added: lgtm, approved

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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

The pull request process is described 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]

New changes are detected. LGTM label has been removed.

[red-hat-konflux]

label added: lgtm, approved

[openshift-ci]

New changes are detected. LGTM label has been removed.

[red-hat-konflux]

label added: lgtm, approved

[openshift-ci]

New changes are detected. LGTM label has been removed.

[red-hat-konflux]

label added: lgtm, approved

[openshift-ci]

New changes are detected. LGTM label has been removed.

[red-hat-konflux]

label added: lgtm, approved

[openshift-ci]

@raptorsun: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.