From 57303f879088b71b008aaed995976ed456f2ae64 Mon Sep 17 00:00:00 2001 From: githubat Date: Fri, 23 Mar 2018 10:00:03 -0700 Subject: [PATCH] Update imperative-command.md (#7699) - Original example (with replaced with my-svc) will result in the following error: error: at least one tcp port specifier must be provided - Use the same example in this section seems ideal --- .../overview/object-management-kubectl/imperative-command.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/overview/object-management-kubectl/imperative-command.md b/docs/concepts/overview/object-management-kubectl/imperative-command.md index a4d62c90a6288..790a615d419c7 100644 --- a/docs/concepts/overview/object-management-kubectl/imperative-command.md +++ b/docs/concepts/overview/object-management-kubectl/imperative-command.md @@ -127,7 +127,7 @@ creation. This is done by piping the output of the `create` command to the `set` command, and then back to the `create` command. Here's an example: ```sh -kubectl create service clusterip -o yaml --dry-run | kubectl set selector --local -f - 'environment=qa' -o yaml | kubectl create -f - +kubectl create service clusterip my-svc --clusterip="None" -o yaml --dry-run | kubectl set selector --local -f - 'environment=qa' -o yaml | kubectl create -f - ``` 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.