Change:
{{< tab name="Zsh" include="included/optional-kubectl-configs-zsh.md" />}} {{< /tabs >}} <ins> ### Install `kubectl convert` plugin {{< include "included/kubectl-convert-overview.md" >}} 1. Download the latest release with the command: ```bash curl -LO https://dl.k8s.io/release/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert ``` 1. Validate the binary (optional) Download the kubectl-convert checksum file: ```bash curl -LO "https://dl.k8s.io/$(curl -L -s https://dl.k8s.io/release/stable.txt)/bin/linux/amd64/kubectl-convert.sha256" ``` Validate the kubectl-convert binary against the checksum file: ```bash echo "$(<kubectl-convert.sha256) kubectl-convert" | sha256sum --check ``` If valid, the output is: ```console kubectl-convert: OK ``` If the check fails, `sha256` exits with nonzero status and prints output similar to: ```bash kubectl-convert: FAILED sha256sum: WARNING: 1 computed checksum did NOT match ``` {{< note >}} Download the same version of the binary and checksum. {{< /note >}} 1. Install kubectl-convert ```bash sudo install -o root -g root -m 0755 kubectl-convert /usr/local/bin/kubectl-convert ``` 1. Verify plugin is successfully installed ```shell kubectl convert --help ``` If you do not see an error, it means the plugin is successfully installed. </ins> ## {{% heading "whatsnext" %}} {{< include "included/kubectl-whats-next.md" >}}

Discussion:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be Update (really, the 3 pages that it links to) to let readers know how to install Why is this needed is now delivered as a plugin, not part of the main binary. v1.22 includes lots of and release v1.22 is the first time lots of readers will really notice the deprecations. However, there has been no API removal release since was moved to be a plugin. Comments /sig cli /kind feature /priority important-soon (IMO)
ref:
<details<summary<emIt's there for the installing</em</summary<pre$ curl -L -I HTTP/2 302 server: nginx date: Wed, 30 Jun 2021 23:06:44 GMT content-type: text/html content-length: 154 location: via: 1.1 google alt-svc: clear </pre</detailsWhere current docs say to fetch (eg) , let's tell them to install as well.
Since kubectl-convert is a separate binary, should reference of the command from page also be removed?
/help I'm willing to revise this issue description if it's not clear how to make these changes.
This request has been marked as needing help from a contributor. Please ensure the request meets the requirements listed . If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : /help Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
what you're asking sounds like a separate issue.
I would like to work on this issue. From what I understand, a new command to download has to be under the first point titled for all the three operating systems something like this. Does verifying checksum step also have to for kubectl-convert?
Yes, we should let readers know how to check that the software they download is genuine.
We should also briefly explain what does (a hyperlink is OK)
/assign
the command line reference page still lists -
How do you install kubectl convert for windows? I don't seem to have it installed.

I'm going to mark as off-topic; the original issue is resolved.
How is this issue resolved/closed? I didn't found anywhere on the docs how to install the plugin/binary, only found this info on a third-party site: This really should be better documented, and there is still a mention of this command on this page without any word about it being deprecated and transformed into a plugin/binary:
Try this link: For me, the top search result is to a page with a section “Install plugin”. I think this issue was OK to close.
Truly, didn't have found this section, thanks But i also didn't expected a deprecated command installation instructions would be directly on the page that teaches how to install the command itself, thought it would be in a or section. Can we at least add the link about on the page that teaches how to ? That what people trying to migrate from 1.22 to 1.23 would find it easier. Opened a PR for this here
I'm on a macbook pro Ventura 13, M1 chip. I followed the instructions using ARM64 version. Step 3 didn't work, so I used this instead: Which worked, but then, ran and got: "Error: exec format error" Am I doing something wrong or does this plugin not work on Mac with M1?
You should try asking in