document plugin resolution as subcommand for builtin commands

[ardaguclu]

This PR adds document for the alpha stage of kubernetes/enhancements#3638

[sftim]

I think content/en/docs/reference/kubectl/kubectl.md is automatically generated; if that's right, then you don't need to send in this change. However, if there's no other documentation, will people know that they could try using it?

[ardaguclu]

I think content/en/docs/reference/kubectl/kubectl.md is automatically generated; if that's right, then you don't need to send in this change. However, if there's no other documentation, will people know that they could try using it?

Thanks @sftim. Shouldn't I add this new environment variable into somewhere to feed this auto generated page content/en/docs/reference/kubectl/kubectl.md?

[LukeMwila]

Hey @sftim @ardaguclu, just following up on the changes to content/en/docs/reference/kubectl/kubectl.md. The docs PRs have to be merged by end of today.

[ardaguclu]

I mimicked the same place in this PR #37788. If there is any other place should be added, I gladly can add there.

[sftim]

Hey @sftim @ardaguclu, just following up on the changes to content/en/docs/reference/kubectl/kubectl.md. The docs PRs have to be merged by end of today.

I checked https://github.com/kubernetes/sig-release/tree/master/releases/release-1.27
The docs PRs have to be ready to merge today. Merges should be done by the start of the 10th of April.

I don't know whether SIG Docs has capacity to get all the pending 1.27 PRs reviewed today. My guess is no.

[LukeMwila]

Hey @sftim @ardaguclu, just following up on the changes to content/en/docs/reference/kubectl/kubectl.md. The docs PRs have to be merged by end of today.

I checked https://github.com/kubernetes/sig-release/tree/master/releases/release-1.27 The docs PRs have to be ready to merge today. Merges should be done by the start of the 10th of April.

I don't know whether SIG Docs has capacity to get all the pending 1.27 PRs reviewed today. My guess is no.

Thanks for the response @sftim, and sorry for the confusion. I meant ready to merge.

[LukeMwila]

/approve

[LukeMwila]

I mimicked the same place in this PR #37788. If there is any other place should be added, I gladly can add there.

I had a look at the previous PR that you referred to. Thanks.

[reylejano]

This will be overwritten when the kubectl reference docs are generated

[divya-mohan0209]

I'm happy to lgtm this change so that this is reflected in the 1.27 change log. However, this will be overwritten during the reference doc generation & I'd advise @ardaguclu to refer to this page for amending the correct files & getting the relevant changes reflected.

/lgtm

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: ea53ac9e142a5906fd0bb6c12492d366e7025334

[divya-mohan0209]

@sftim / @reylejano / @tengqm : Please advise if the information I've supplemented wrt the guide is incorrect.

[tengqm]

/approve

The auto-generated contents is here: static/docs/reference/generated/kubectl/

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LukeMwila, tengqm

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:

• content/en/OWNERS [tengqm]

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