OLS-3683 OLS-3684: regenerate bundle for agentic integration

[blublinsky]

Description

Summary

• Regenerated bundle CSV to include new operator flags (--agentic-sandbox-image) and agentic integration resources from OLS-3683/OLS-3684
• Updated all Konflux-built operand images to latest CI digests as part of bundle regeneration

Type of change

• [ x] Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue #
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.

Summary by CodeRabbit

• Chores
  • Updated the Lightspeed operator and associated Lightspeed component image references to newer builds.
  • Refreshed image digests for the operator and related components to keep integrity metadata current.
  • Updated release/package metadata (including annotation timestamps) for the operator bundle.

[openshift-ci-robot]

@blublinsky: This pull request references OLS-3683 which is a valid jira issue.

This pull request references OLS-3684 which is a valid jira issue.

Details

In response to this:

Description

Summary

• Regenerated bundle CSV to include new operator flags (--agentic-sandbox-image) and agentic integration resources from OLS-3683/OLS-3684
• Updated all Konflux-built operand images to latest CI digests as part of bundle regeneration

Type of change

• [ x] Refactor
• New feature
• Bug fix
• CVE fix
• Optimization
• Documentation Update
• Configuration Update
• Bump-up dependent library

Related Tickets & Documents

• Related Issue #
• Closes #

Checklist before requesting a review

• I have performed a self-review of my code.
• PR has passed all pre-merge test jobs.
• If it is a core feature, I have added thorough tests.

Testing

• Please provide detailed steps to perform tests related to this code change.
• How were the fix/results from this change verified? Please provide relevant screenshots or results.

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 openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

Warning

Review limit reached

@blublinsky, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 31e3a25f-ae43-4b3e-bfba-8f1f19b28339

📥 Commits

Reviewing files that changed from the base of the PR and between ed5cf4a and c9ef6ce.

⛔ Files ignored due to path filters (1)

• related_images.json is excluded by !related_images.json

📒 Files selected for processing (2)

• bundle/manifests/lightspeed-operator.clusterserviceversion.yaml
• config/default/deployment-patch.yaml

📝 Walkthrough

Walkthrough

The ClusterServiceVersion updates its creation timestamp and replaces Lightspeed operator and component image references with new quay.io digests in controller-manager arguments and relatedImages.

Changes

CSV image reference refresh

Layer / File(s)	Summary
Update CSV metadata and image references bundle/manifests/lightspeed-operator.clusterserviceversion.yaml	The CSV timestamp, controller-manager component image arguments, manager image, and corresponding relatedImages entries are updated to new quay.io image digests. The rhokp reference remains unchanged.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• openshift/lightspeed-operator#1870: Updates the same CSV’s agentic console and alerts-adapter image references.

Suggested reviewers: joshuawilson, xrajesh, raptorsun

🚥 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 clearly matches the main change: regenerating the bundle for agentic integration tied to OLS-3683 and OLS-3684.
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.

✨ 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.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joshuawilson 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

[coderabbitai]

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 `@bundle/manifests/lightspeed-operator.clusterserviceversion.yaml`:
- Around line 1004-1019: Before merging, validate that every production image
referenced by the CSV arguments and relatedImages—including the operator and
operand images under
quay.io/redhat-user-workloads/crt-nshift-lightspeed-tenant—is promoted and
pullable through the supported release mirror for disconnected OLM
installations. Replace any staging-only image references or digests with
approved mirrorable release artifacts, keeping the CSV argument entries and
relatedImages aligned.

🪄 Autofix (Beta)

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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 6cb6714e-6697-4528-985f-452379fa7a08

📥 Commits

Reviewing files that changed from the base of the PR and between 450e549 and dfa7f15.

⛔ 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

[raptorsun]

we can switch back to production registry registry.redhat.io/openshift-lightspeed/
our releases are back to normal

[raptorsun]

production registry is not available. we keep quay.io

[raptorsun]

production registry is not available. we keep quay.io

[openshift-ci]

@blublinsky: 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.

[openshift-ci]

PR needs rebase.

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.