CONSOLE-5118: Add OLS integration for cluster update workflows

[fao89]

Implements OpenShift Lightspeed AI assistance integration into cluster settings page to provide contextual help during cluster update workflows.

Features:

• UpdateWorkflowOLSButton component with 4 workflow phase support
• Precheck: Pre-update validation and readiness assessment
• Failure: Error analysis and troubleshooting guidance
• Status: Real-time update progress monitoring assistance
• Success: Post-update verification and validation help

The integration uses the official lightspeed-console plugin API to open the OLS chatbox with context-aware prompts and cluster data attachments. Each workflow phase provides tailored AI prompts and exports relevant cluster resources (ClusterVersion) as YAML for comprehensive analysis.

Note: E2E test file (cluster-settings-page.ts) excluded from backport as Playwright E2E framework is not available in release-4.22.

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com
Signed-off-by: Fabricio Aguiar fabricio.aguiar@gmail.com

(cherry picked from commit 60f1c71)

Analysis / Root cause:

Solution description:

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@fao89: This pull request references CONSOLE-5118 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Implements OpenShift Lightspeed AI assistance integration into cluster settings page to provide contextual help during cluster update workflows.

Features:

• UpdateWorkflowOLSButton component with 4 workflow phase support
• Precheck: Pre-update validation and readiness assessment
• Failure: Error analysis and troubleshooting guidance
• Status: Real-time update progress monitoring assistance
• Success: Post-update verification and validation help

The integration uses the official lightspeed-console plugin API to open the OLS chatbox with context-aware prompts and cluster data attachments. Each workflow phase provides tailored AI prompts and exports relevant cluster resources (ClusterVersion) as YAML for comprehensive analysis.

Note: E2E test file (cluster-settings-page.ts) excluded from backport as Playwright E2E framework is not available in release-4.22.

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com
Signed-off-by: Fabricio Aguiar fabricio.aguiar@gmail.com

(cherry picked from commit 60f1c71)

Analysis / Root cause:

Solution description:

Screenshots / screen recording:

Test setup:

Test cases:

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:

Reviewers and assignees:

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.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• frontend/OWNERS

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