Add subresource support to kubectl

[nikhita]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add a new flag --subresource to kubectl commands like get, patch, edit and replace commands to allow fetching and updating subresources like status, scale, etc.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2590-kubectl-subresource
• Discussion Link:
  • Discussion in the POC PR - kubectl: support --subresource flag kubernetes#99556
  • mailing list/meeting link: https://youtu.be/zUa7dudYCQM?t=299
• Primary contact (assignee): @nikhita @MadhavJivrajani
• Responsible SIGs: SIG CLI
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.24
  • Beta release target (x.y): v1.27
  • Stable release target (x.y): v1.33
• Alpha
  • KEP (k/enhancements) update PR(s):
    • kubectl subresource KEP #2600
  • Code (k/k) update PR(s):
    • apiserver changes - kubectl: apiserver changes to add --subresource support kubernetes#103516
    • kubectl changes - kubectl: support --subresource flag kubernetes#99556
  • Docs (k/website) update PR(s):
    • Document kubectl subresource support website#32604
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-2590: graduate kubectl subresource support to beta #3729
  • Code (k/k) update PR(s):
    • kubectl: Change subresource flag to beta kubernetes#116595
    • test/e2e: Add e2e tests for kubectl --subresource kubernetes#116590
    • test/e2e: Fix flaking subresource test kubernetes#116619
    • add --subresource to kubectl apply kubernetes#127634
    • [FG:InPlacePodVerticalScaling] Remove restrictions on subresource flag in kubectl commands kubernetes#128296
  • Docs (k/website) update(s):
    • reference/kubectl: Update docs for moving kubectl subresource to beta website#39828
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-2590: graduate kubectl subresource support to stable #4468
    • KEP 2590: Graduate kubectl subresource to GA #5079
    • KEP 2590: metadata update #5162
    • KEP-2590: update supported subresources list #5179
    • KEP-2590: mark as implemented #5192
  • Code (k/k) update PR(s):
    • Update kubectl subresource to stable kubernetes#130238
  • Docs (k/website) update(s):
    • Update kubectl subresource documentation website#49824

/sig cli
/assign @nikhita @ykakarap
cc @eddiezane @soltysh @seans3 @pwittrock

[JamesLaverack]

/stage alpha
/milestone v1.22

[salaxander]

Hi @nikhita , 1.22 enhancements team here!

For the enhancement to be included in the milestone, it must meet the following criteria:

• The KEP must be merged in an implementable state
• [DONE] The KEP must have test plans
• [DONE] The KEP must have graduation criteria
• The KEP must have a production readiness review

In order to move forward in 1.22 we'd need to get the KEP merged as well as a production readiness review before enhancements freeze on 5/13. Let us know if there's anything we can do to help before then.

Thanks!!

[ykakarap]

Hi @salaxander, @nikhita and I are working in this together.
Thanks for the heads-up on the pending items for the KEP :).

Regarding the production readiness review, the KEP doc has a section by the same name. Does this section satisfy the required criteria? If not, can you let us know what is missing from it.
Thanks!

[salaxander]

Hi @ykakarap! - Here's the full documentation on the production readiness review process -> https://github.com/kubernetes/community/blob/master/sig-architecture/production-readiness.md

[soltysh]

#2600 merged so we should be all good now.

[chrisnegus]

Hi @nikhita 👋 1.22 Docs Shadow here.
This enhancement is marked as Needs Docs for the 1.22 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.22 in the kubernetes/website repo. This PR can be just a placeholder at this time and must be created before Fri July 9, 11:59 PM PDT.

Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

[ykakarap]

@chrisnegus Thanks for the heads-up! :)

Will follow the steps to do it.

[salaxander]

Hi @nikhita and @ykakarap - Just checking in as we're about 2 weeks away from 1.22 code freeze. Are there any open or merged k/k PRs we should be tracking for this? Thanks!!