Skip to content

OLS-3210: Remove pf5/4-19 console images from related_images.json and bundle#1730

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
blublinsky:bundle-console-multi-image
Jun 19, 2026
Merged

OLS-3210: Remove pf5/4-19 console images from related_images.json and bundle#1730
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
blublinsky:bundle-console-multi-image

Conversation

@blublinsky

@blublinsky blublinsky commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

Description

Summary
Bundle follow-up for OLS-3210 / epic OLS-3205: align the OLM bundle with the single-console-image operator merged in #1705.

Operator code no longer accepts --console-image-pf5 or --console-image-4-19. The CSV still passed those flags and listed pf5/4-19 in relatedImages, which caused OLM installs to CrashLoop. This PR updates related_images.json and regenerates the bundle.

Changes
Remove lightspeed-console-plugin-pf5 and lightspeed-console-plugin-4-19 from related_images.json
Regenerate bundle (make bundle BUNDLE_TAG=1.1.1):
Drop --console-image-pf5 and --console-image-4-19 from the operator deployment args in the CSV
Drop pf5/4-19 entries from spec.relatedImages
Keep a single --console-image and lightspeed-console-plugin related imageSummary
Bundle follow-up for OLS-3210 / epic OLS-3205: align the OLM bundle with the single-console-image operator merged in #1705.

Operator code no longer accepts --console-image-pf5 or --console-image-4-19. The CSV still passed those flags and listed pf5/4-19 in relatedImages, which caused OLM installs to CrashLoop. This PR updates related_images.json and regenerates the bundle.

Changes
Remove lightspeed-console-plugin-pf5 and lightspeed-console-plugin-4-19 from related_images.json
Regenerate bundle (make bundle BUNDLE_TAG=1.1.1):
Drop --console-image-pf5 and --console-image-4-19 from the operator deployment args in the CSV
Drop pf5/4-19 entries from spec.relatedImages
Keep a single --console-image and lightspeed-console-plugin related image

Type of change

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

Related Tickets & Documents

https://redhat.atlassian.net/browse/OLS-3210

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 operator console plugin image references by consolidating to a single main image variant.
  • Documentation
    • Clarified TLS certificate secret behavior for KeyCertSecretRef when the optional ca.crt key is not present.
  • Tests
    • Removed the Tekton integration E2E pipeline used for console pre-commits on ephemeral clusters.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 18, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 18, 2026

Copy link
Copy Markdown

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

Details

In response to this:

Description

Summary
Bundle follow-up for OLS-3210 / epic OLS-3205: align the OLM bundle with the single-console-image operator merged in #1705.

Operator code no longer accepts --console-image-pf5 or --console-image-4-19. The CSV still passed those flags and listed pf5/4-19 in relatedImages, which caused OLM installs to CrashLoop. This PR updates related_images.json and regenerates the bundle.

Changes
Remove lightspeed-console-plugin-pf5 and lightspeed-console-plugin-4-19 from related_images.json
Regenerate bundle (make bundle BUNDLE_TAG=1.1.1):
Drop --console-image-pf5 and --console-image-4-19 from the operator deployment args in the CSV
Drop pf5/4-19 entries from spec.relatedImages
Keep a single --console-image and lightspeed-console-plugin related imageSummary
Bundle follow-up for OLS-3210 / epic OLS-3205: align the OLM bundle with the single-console-image operator merged in #1705.

Operator code no longer accepts --console-image-pf5 or --console-image-4-19. The CSV still passed those flags and listed pf5/4-19 in relatedImages, which caused OLM installs to CrashLoop. This PR updates related_images.json and regenerates the bundle.

Changes
Remove lightspeed-console-plugin-pf5 and lightspeed-console-plugin-4-19 from related_images.json
Regenerate bundle (make bundle BUNDLE_TAG=1.1.1):
Drop --console-image-pf5 and --console-image-4-19 from the operator deployment args in the CSV
Drop pf5/4-19 entries from spec.relatedImages
Keep a single --console-image and lightspeed-console-plugin related image

Type of change

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

Related Tickets & Documents

https://redhat.atlassian.net/browse/OLS-3210

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

coderabbitai Bot commented Jun 18, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: fdb4347d-6173-4a5f-bdb7-20fc4646f851

📥 Commits

Reviewing files that changed from the base of the PR and between 0884eb4 and fcfc033.

⛔ Files ignored due to path filters (1)
  • related_images.json is excluded by !related_images.json
📒 Files selected for processing (2)
  • .tekton/integration-tests/pipelines/lightspeed-console-e2e-test-pipeline-pf5.yaml
  • bundle/manifests/lightspeed-operator.clusterserviceversion.yaml
💤 Files with no reviewable changes (1)
  • .tekton/integration-tests/pipelines/lightspeed-console-e2e-test-pipeline-pf5.yaml
🚧 Files skipped from review as they are similar to previous changes (1)
  • bundle/manifests/lightspeed-operator.clusterserviceversion.yaml

📝 Walkthrough

Walkthrough

The ClusterServiceVersion manifest updates the TLS certificate secret reference CRD description to clarify behavior when the optional ca.crt key is absent, and removes the pf5 and 4-19 console-plugin variant image entries from the relatedImages list. The Tekton pipeline for console E2E testing on pf5 environments is entirely deleted.

Changes

CSV Manifest: Console Plugin Consolidation

Layer / File(s) Summary
Console plugin images and ca.crt documentation
bundle/manifests/lightspeed-operator.clusterserviceversion.yaml
The relatedImages section removes the pf5 and 4-19 variant entries for lightspeed-console-plugin, leaving only the primary image entry. The CRD description for the optional ca.crt key in TLS certificate secret references is updated to specify that the console proxy falls back to the default system trust store when ca.crt is not provided.

Tekton Pipeline Removal

Layer / File(s) Summary
Console E2E test pipeline deletion
.tekton/integration-tests/pipelines/lightspeed-console-e2e-test-pipeline-pf5.yaml
The entire ols-console-pre-commits Tekton Pipeline resource is removed. This pipeline provisioned ephemeral clusters, installed operator bundles, ran Cypress E2E tests, and exported logs for pf5-variant console plugin environments.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested reviewers

  • 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 directly references the main objective: removing pf5/4-19 console images from related_images.json and the bundle, which aligns with the actual changes made to the ClusterServiceVersion manifest.
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

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

@openshift-ci openshift-ci Bot requested review from bparees and raptorsun June 18, 2026 08:38
@blublinsky blublinsky force-pushed the bundle-console-multi-image branch 2 times, most recently from 0884eb4 to ab7b72d Compare June 18, 2026 10:51
@openshift-ci openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 18, 2026
@blublinsky blublinsky force-pushed the bundle-console-multi-image branch from ab7b72d to a3e5cbd Compare June 18, 2026 14:19
@openshift-ci openshift-ci Bot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Jun 18, 2026
@blublinsky blublinsky force-pushed the bundle-console-multi-image branch from a3e5cbd to fcfc033 Compare June 19, 2026 07:37
@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 19, 2026
@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown

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

@JoaoFula

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 19, 2026
@blublinsky

Copy link
Copy Markdown
Contributor Author

/approve

@openshift-ci

openshift-ci Bot commented Jun 19, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: blublinsky

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 19, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit b09aced into openshift:main Jun 19, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants