Skip to content

proposal for must-gather agentic debugging via MCP#2064

Draft
sakshiep1 wants to merge 1 commit into
openshift:masterfrom
sakshiep1:must-gather-agentic-debugging
Draft

proposal for must-gather agentic debugging via MCP#2064
sakshiep1 wants to merge 1 commit into
openshift:masterfrom
sakshiep1:must-gather-agentic-debugging

Conversation

@sakshiep1

Copy link
Copy Markdown

Summary

Enhancement proposal for must-gather agentic debugging adapter with MCP server and IntelliAide integration.

What this proposes

When a user sets agenticDebuggingEnabled: true on a MustGather CR, the operator - after a successful gather Job - will:

  1. Deploy a shared MCP server (using the openshift-mcp-server image with only the openshift/mustgather toolset enabled) that mounts the same PVC
  2. Create a Lightspeed Proposal CR that triggers a sandboxed agent to perform IntelliAide RCA against the collected data

The agent never requires cluster-admin privileges - it accesses must-gather data exclusively through MCP tool calls over HTTP.

Key design decisions

  • Shared MCP server: Single Deployment serves all collections via subPath isolation (avoids per-CR pod waste)
  • MCP server image: registry.redhat.io/openshift-mcp-beta/openshift-mcp-server-rhel9
  • Opt-in + TechPreview gated: agenticDebuggingEnabled defaults to false; feature gated for initial releases
  • Graceful degradation: If Lightspeed is not installed, operator logs and skips - MustGather completes normally
  • Single PVC scope: Initial implementation supports one PVC per operator namespace; multiple PVC support deferred
  • User owns PVC lifecycle: Operator does not create or delete PVCs

Components involved

  • openshift/must-gather-operator - new fields, MCP server management, Proposal creation
  • openshift/openshift-mcp-server - consumed as container image (no code changes)
  • openshift/lightspeed-agentic-sandbox - consumed via existing Proposal/AnalysisResult APIs (no code changes needed from us)

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 17, 2026
@openshift-ci

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

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

openshift-ci Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

[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 joepvd 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

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

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant