Skip to content

MG-141: Add tool for cluster state summary #90

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
swghosh wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

MG-141: Add tool for cluster state summary #90

swghosh wants to merge 6 commits into from

Conversation

@swghosh
Copy link
Member

@swghosh swghosh commented Dec 23, 2025

Adapted from https://github.com/openshift/oc/blob/0c09391d89b24f45dc606eee749e67d9b52c9f70/pkg/cli/admin/mustgather/summary.go#L17-L52

oc CLI provides a human readable summary of cluster state when running a must-gather, it is reasonable to include the same as an MCP tool.

harche and others added 6 commits November 4, 2025 13:48
@harche
Add nodes_debug_exec tool in pkg/ocp package
dbe51ab
@swghosh
move node tools into pkg/toolsets/openshift/nodes
abd1c31 
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh
make k.canIUse and exported func
9b6ac5b 
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh
implement plan_mustgather in must-gather OCP toolset
cb29fed
@swghosh
add persistent storage for plan_mg optionally
d2bf1e9 
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@swghosh @claude
Add ClusterStateSummary tool
8cf42d9 
- adapted from https://github.com/openshift/oc/blob/0c09391d89b24f45dc606eee749e67d9b52c9f70/pkg/cli/admin/mustgather/summary.go

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Swarup Ghosh <swghosh@redhat.com>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 23, 2025
@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 Dec 23, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 23, 2025 •
edited by openshift-ci bot
Loading

@swghosh: This pull request references MG-141 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:

Adapted from https://github.com/openshift/oc/blob/0c09391d89b24f45dc606eee749e67d9b52c9f70/pkg/cli/admin/mustgather/summary.go#L17-L52

oc CLI provides a human readable summary of cluster state when running a must-gather, it is reasonable to include the same as an MCP tool.

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
Copy link

openshift-ci bot commented Dec 23, 2025

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-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 23, 2025
@openshift-merge-robot
Copy link

openshift-merge-robot commented Dec 23, 2025

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.

@openshift-ci
Copy link

openshift-ci bot commented Dec 23, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

Reviewers

No reviews

Assignees

No one assigned

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@swghosh @openshift-ci-robot @openshift-merge-robot @harche