Add debug plugin

[aylei]

Hi there, thanks for reviewing my PR! Please don't hesitate to point out areas where I need to change.

Plugin Home Page

Signed-off-by: Aylei rayingecho@gmail.com

---

Checklist for plugin developers:

• Read the Plugin Naming Guide (for new plugins)
• Verify the installation from URL or a local archive works (kubectl krew install --manifest=[...] --archive=[...])

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aylei
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: juanvallejo

If they are not already assigned, you can assign the PR to them by writing /assign @juanvallejo in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

[ahmetb]

This name is too generic. Please choose something more unique and descriptive. Also there’s been a proposal to create an official debug command, which might be still going on: kubernetes/kubernetes#45922

[aylei]

Thank you for your advice!
Actually, the project homepage x-ref the related KEP(Troubleshooting Running Pods), and the purpose of this plugin is help the users to do the similar stuff before this KEP completes and help the users who still using the old version of kubernetes after the KEP completes.
How about kubectl-debug-pod? The form kubectl debug pod will be shadowed when debug command is added officially, and kubectl debug-pod is fairly descriptive I guess.

[ahmetb]

I agree debug-container or debug-pod is better (debug-pod would be my preference). Sadly first-class kubectl commands can claim vauge/broad terminology like "debug" but I think we should be more careful.

Does this cause a problem with your documentation etc. Are you planning to go make the name change there as well?

[aylei]

Does this cause a problem with your documentation etc.

Not quite, I will add documents to explain the krew part about the slightly different name and it's a not a burden for me.

Are you planning to go make the name change there as well?

I prefer not, changing name can be troublesome for me and existing adopters.

[aylei]

I realize that I have to update some codes to support both kubectl debug-pod and kubectl debug command suggestions, so I will close this PR now and open another PR in the next release of my project.

[ahmetb]

Thanks! Expecting a new PR soon, happy to discuss what would be a more appropriate name.