Improve clarity of kubectl Cheat Sheet with version information

[rainbowBPF2]

Feedback a confusing point about kubectl command on page:
https://kubernetes.io/docs/reference/kubectl/cheatsheet/#formatting-output

"kubectl events " command seems just available in k8s-v1.26 release version, while below v1.26 not work yet.

so a brief tip or comment on the page will be easy to understand.

FYI.

[T-Lakshmi]

Page: https://kubernetes.io/docs/reference/kubectl/cheatsheet/#formatting-output
/language en
/kind suggestion

[k8s-ci-robot]

@T-Lakshmi: The label(s) kind/suggestion cannot be applied, because the repository doesn't have them.

In response to this:

Page: https://kubernetes.io/docs/reference/kubectl/cheatsheet/#formatting-output
/language en
/kind suggestion

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.

[dipesh-rawat]

In my opinion, the cheat sheet is accurate for Kubernetes v1.26. However, if someone needs to refer to older documentation, they can access it by using the version selector option in the navigation bar.
To improve clarity, the cheat sheet could integrate details from https://kubernetes.io/docs/home/supported-doc-versions/ and provide explicit links within the content body to the other available versions. This approach would be more effective than simply relying on the version selector in the top navigation. Would folks consider this suggestion beneficial?

[dipesh-rawat]

/retitle Improve clarity of kubectl Cheat Sheet with version information

[sftim]

I'd like to see a shortcode that renders as helper text to steer people to the right documentation, and a link to available versions.

See https://kubernetes.io/docs/setup/production-environment/container-runtimes/ for an example where I'd use this:

If you are running a version of Kubernetes other than v1.26, check the documentation for that version.

we could replace that text with an even more helpful shortcode.

[sftim]

We could add a comment that this is accurate for this version of the docs.

/priority backlog

[sftim]

I recommend the simple comment approach. We can still use version shortcodes, eg {{< skew currentVersion >}} in the comment.
/triage accepted

[mrgiles]

/assign

[mrgiles]

FYI @sftim