Add new plugin: why

[rameshsurapathi]

Plugin: kubectl-why

What does it do?
Turns Kubernetes failures into plain-English diagnosis with evidence and fix commands.
Homepage: https://github.com/rameshsurapathi/kubectl-why
License: MIT
Checklist:

• Binary is named kubectl-why (auto-discovered as kubectl plugin)
• Binaries are statically compiled (CGO_ENABLED=0)
• 5 platform targets (darwin/linux amd64+arm64, windows amd64)
• SHA256 checksums verified from GitHub Release
• Plugin tested locally with krew install --manifest

[ahmetb]

🤖 Beep beep! I’m a robot speaking on behalf of @ahmetb. 🤖

---

Thanks for submitting your kubectl plugin to Krew!
One of the krew-index maintainers will review it soon. Note that the reviews for new plugin submissions may take a few days.

In the meanwhile, here are a few tips to make your plugin manifest better:

• Make sure your plugin follows the best practices.
• Eliminate redundant wording form shortDescription (it should be max 50 characters).
• Try to word wrap your description to 80-character lines (no usage examples, please).

Thanks for your patience!
/kind new-plugin

[linux-foundation-easycla]

• ❌ - login: @rameshsurapathi / name: rameshsurapathi . The commit (7209c27) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

• OWNERS

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

[k8s-ci-robot]

Welcome @rameshsurapathi!

It looks like this is your first PR to kubernetes-sigs/krew-index 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/krew-index has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[ahmetb]

Sorry there are a dozen plugins that do this already. Please look at them first.

[ahmetb]

Thanks for submitting kubectl-why! A few things to be aware of:

Review timeline: Initial plugin submissions can take a significant amount of time to review. Maintainers are receiving a very high volume of submissions — many vibe-coded tools with significant functional overlap — so please be patient. Reviewers assess whether each plugin is a good fit and whether the problem is already solved by existing plugins.

triage — fast diagnostics for failed pods, aggregates status/events/crash logs
crashloop — correlates crash events, termination state, previous logs
crashwatch — monitors CrashLoopBackOff pods
sick-pods — debug info for not-ready pods
kopilot — AI-powered plain-English diagnosis
Please try these out. If kubectl-why offers meaningful differentiation (safety-tagged remediation, relationship tracing, JSON output), update the PR description to clearly articulate that. Otherwise, consider contributing to one of the existing projects instead.