Improve kubectl plugin resolution for non-shadowing subcommands

[ardaguclu]

Enhancement Description

• One-line enhancement description (can be used as a release note): Improve kubectl plugin resolution for non-shadowing subcommands
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cli/3638-built-in-command-shadowing/README.md
• Discussion Link: September 21, 2022 sig-cli bi-weekly meeting
• Primary contact (assignee): @ardaguclu
• Responsible SIGs: sig-cli
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.27
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3638: Enable built-in command shadowing by plugins #3639
  • Code (k/k) update PR(s):
    • Enable plugin resolution as subcommand for selected builtin commands kubernetes#116293
  • Docs (k/website) update PR(s):
    • document plugin resolution as subcommand for builtin commands website#39969

Tasks

No tasks being tracked yet.

[ardaguclu]

/milestone v1.27

[k8s-ci-robot]

@ardaguclu: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone v1.27

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/test-infra repository.

[ardaguclu]

/sig cli

[soltysh]

/assign @ardaguclu

[soltysh]

/milestone v1.27
/label lead-opted-in

[soltysh]

/stage alpha

[Atharva-Shinde]

Hello @ardaguclu 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage alpha for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

• Add response for this question in the Scalability questionnaire of the KEP readme

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[ardaguclu]

Thanks @Atharva-Shinde. I added response for the newly added Scalability question. Is there anything further I can do aside from waiting for PRR review?

[Atharva-Shinde]

Hey @ardaguclu, aside from getting PRR approved, everything for this KEP looks good for now :)

[ardaguclu]

Thanks @Atharva-Shinde

[Atharva-Shinde]

@ardaguclu With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

The status of this enhancement is marked as tracked. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[sftim]

Docs PR: kubernetes/website#39800

[LukeMwila]

Hi @ardaguclu, I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

Please feel free to reach out with any questions. Thanks!

[Atharva-Shinde]

Hey again @ardaguclu 👋 Enhancements team here,
Just checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are fully merged by the code freeze deadline.
  • Enable plugin resolution as subcommand for selected builtin commands kubernetes#116293

Also please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!