From d69f6b23535d3f1575b9da842e9e6d2a790fd412 Mon Sep 17 00:00:00 2001 From: nepomucen Date: Thu, 15 Nov 2018 02:45:18 +0100 Subject: [PATCH] Fix missing selector subcommand (#10982) For accuracy the second command "kubectl set" in the pipeline under the example`s breakdown should contain subcommand: selector --- .../overview/object-management-kubectl/imperative-command.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/object-management-kubectl/imperative-command.md b/content/en/docs/concepts/overview/object-management-kubectl/imperative-command.md index d0cbe8c839..38b194d2a4 100644 --- a/content/en/docs/concepts/overview/object-management-kubectl/imperative-command.md +++ b/content/en/docs/concepts/overview/object-management-kubectl/imperative-command.md @@ -136,7 +136,7 @@ kubectl create service clusterip my-svc --clusterip="None" -o yaml --dry-run | k ``` 1. The `kubectl create service -o yaml --dry-run` command creates the configuration for the Service, but prints it to stdout as YAML instead of sending it to the Kubernetes API server. -1. The `kubectl set --local -f - -o yaml` command reads the configuration from stdin, and writes the updated configuration to stdout as YAML. +1. The `kubectl set selector --local -f - -o yaml` command reads the configuration from stdin, and writes the updated configuration to stdout as YAML. 1. The `kubectl create -f -` command creates the object using the configuration provided via stdin. ## Using `--edit` to modify objects before creation