@@ -379,14 +379,26 @@ to locate use of deprecated APIs.
379
379
* Update custom integrations and controllers to call the non-deprecated APIs
380
380
* Change YAML files to reference the non-deprecated APIs
381
381
382
- You can use the ` kubectl-convert ` command (` kubectl convert ` prior to v1.20)
383
- to automatically convert an existing object:
382
+ You can use the ` kubectl convert ` command to automatically convert an existing object:
384
383
385
- ` kubectl- convert -f <file> --output-version <group>/<version> ` .
384
+ ` kubectl convert -f <file> --output-version <group>/<version> ` .
386
385
387
386
For example, to convert an older Deployment to ` apps/v1 ` , you can run:
388
387
389
- ` kubectl- convert -f ./my-deployment.yaml --output-version apps/v1 `
388
+ ` kubectl convert -f ./my-deployment.yaml --output-version apps/v1 `
390
389
391
- Note that this may use non-ideal default values. To learn more about a specific
390
+ This conversion may use non-ideal default values. To learn more about a specific
392
391
resource, check the Kubernetes [ API reference] ( /docs/reference/kubernetes-api/ ) .
392
+
393
+ {{< note >}}
394
+ The ` kubectl convert ` tool is not installed by default, although
395
+ in fact it once was part of ` kubectl ` itself. For more details, you can read the
396
+ [ deprecation and removal issue] ( https://github.com/kubernetes/kubectl/issues/725 )
397
+ for the built-in subcommand.
398
+
399
+ To learn how to set up ` kubectl convert ` on your computer, visit the page that is right for your
400
+ operating system:
401
+ [ Linux] ( /docs/tasks/tools/install-kubectl-linux/#install-kubectl-convert-plugin ) ,
402
+ [ macOS] ( /docs/tasks/tools/install-kubectl-macos/#install-kubectl-convert-plugin ) , or
403
+ [ Windows] ( /docs/tasks/tools/install-kubectl-windows/#install-kubectl-convert-plugin ) .
404
+ {{< /note >}}
0 commit comments