From 9fd549b12c6896b311a55de477691ff910071519 Mon Sep 17 00:00:00 2001 From: Andres Caro Date: Thu, 24 Sep 2020 08:05:24 -0500 Subject: [PATCH] Update the run command to refer to pod creation The "run" command refers to deployment creation and it should refer to pod creation --- .../docs/tasks/manage-kubernetes-objects/imperative-command.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/manage-kubernetes-objects/imperative-command.md b/content/en/docs/tasks/manage-kubernetes-objects/imperative-command.md index f8403dec17..a51b5664ba 100644 --- a/content/en/docs/tasks/manage-kubernetes-objects/imperative-command.md +++ b/content/en/docs/tasks/manage-kubernetes-objects/imperative-command.md @@ -37,7 +37,7 @@ The `kubectl` tool supports verb-driven commands for creating some of the most c object types. The commands are named to be recognizable to users unfamiliar with the Kubernetes object types. -- `run`: Create a new Deployment object to run Containers in one or more Pods. +- `run`: Create a new Pod to run a Container. - `expose`: Create a new Service object to load balance traffic across Pods. - `autoscale`: Create a new Autoscaler object to automatically horizontally scale a controller, such as a Deployment.