Skip to content

OTA-1927: Eval cluster update prompts#2908

Open
fao89 wants to merge 1 commit intoopenshift:mainfrom
fao89:OTA-1927
Open

OTA-1927: Eval cluster update prompts#2908
fao89 wants to merge 1 commit intoopenshift:mainfrom
fao89:OTA-1927

Conversation

@fao89
Copy link
Copy Markdown
Member

@fao89 fao89 commented Apr 29, 2026

Add comprehensive MCP test scenarios to evaluation dataset for validating OpenShift cluster update workflow AI responses. These scenarios establish quality benchmarks for LLM outputs across different update phases.

Test Scenarios Added (conv_798-802):

  • Precheck: Pre-upgrade validation and readiness assessment Comprehensive analysis of cluster health, available updates, and upgrade blockers before initiating updates

  • Precheck-Specific: Targeted upgrade path validation Validates specific version availability and upgrade feasibility for planned update targets

  • No-Updates: Cluster health assessment at latest version Health monitoring and operational status when no updates are available in current channel

  • Progress: Real-time upgrade progress monitoring Tracks upgrade progress with component status, timeline analysis, and ETA calculations during active updates

  • Troubleshoot: Upgrade failure diagnosis and remediation Root cause analysis and conservative troubleshooting guidance for failed or stuck upgrade scenarios

Each scenario includes:

  • Complete analysis prompts with constraints and requirements
  • Full ClusterVersion YAML data as attachments
  • Full ClusterOperator YAML data as attachments
  • Expected responses with Summary and TL;DR sections
  • Real cluster data from production-like scenarios

These scenarios mirror the CONSOLE-5118 OLS integration workflow phases and provide the evaluation baseline for cluster update AI assistance.

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com

Ref: openshift/console#16131

Add comprehensive MCP test scenarios to evaluation dataset for validating
OpenShift cluster update workflow AI responses. These scenarios establish
quality benchmarks for LLM outputs across different update phases.

Test Scenarios Added (conv_798-802):
- Precheck: Pre-upgrade validation and readiness assessment
  Comprehensive analysis of cluster health, available updates, and
  upgrade blockers before initiating updates

- Precheck-Specific: Targeted upgrade path validation
  Validates specific version availability and upgrade feasibility
  for planned update targets

- No-Updates: Cluster health assessment at latest version
  Health monitoring and operational status when no updates are
  available in current channel

- Progress: Real-time upgrade progress monitoring
  Tracks upgrade progress with component status, timeline analysis,
  and ETA calculations during active updates

- Troubleshoot: Upgrade failure diagnosis and remediation
  Root cause analysis and conservative troubleshooting guidance
  for failed or stuck upgrade scenarios

Each scenario includes:
- Complete analysis prompts with constraints and requirements
- Full ClusterVersion YAML data as attachments
- Full ClusterOperator YAML data as attachments
- Expected responses with Summary and TL;DR sections
- Real cluster data from production-like scenarios

These scenarios mirror the CONSOLE-5118 OLS integration workflow phases
and provide the evaluation baseline for cluster update AI assistance.

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

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 29, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 29, 2026

@fao89: This pull request references OTA-1927 which is a valid jira issue.

Details

In response to this:

Add comprehensive MCP test scenarios to evaluation dataset for validating OpenShift cluster update workflow AI responses. These scenarios establish quality benchmarks for LLM outputs across different update phases.

Test Scenarios Added (conv_798-802):

  • Precheck: Pre-upgrade validation and readiness assessment Comprehensive analysis of cluster health, available updates, and upgrade blockers before initiating updates

  • Precheck-Specific: Targeted upgrade path validation Validates specific version availability and upgrade feasibility for planned update targets

  • No-Updates: Cluster health assessment at latest version Health monitoring and operational status when no updates are available in current channel

  • Progress: Real-time upgrade progress monitoring Tracks upgrade progress with component status, timeline analysis, and ETA calculations during active updates

  • Troubleshoot: Upgrade failure diagnosis and remediation Root cause analysis and conservative troubleshooting guidance for failed or stuck upgrade scenarios

Each scenario includes:

  • Complete analysis prompts with constraints and requirements
  • Full ClusterVersion YAML data as attachments
  • Full ClusterOperator YAML data as attachments
  • Expected responses with Summary and TL;DR sections
  • Real cluster data from production-like scenarios

These scenarios mirror the CONSOLE-5118 OLS integration workflow phases and provide the evaluation baseline for cluster update AI assistance.

Co-Authored-By: Claude Sonnet 4.5 noreply@anthropic.com

Ref: openshift/console#16131

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 openshift-ci Bot requested review from blublinsky and raptorsun April 29, 2026 15:44
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 29, 2026

[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 bparees 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:

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

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 29, 2026

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants