From 35036d2778b6b5ea5d6d810bf03a324d58b0fd4f Mon Sep 17 00:00:00 2001 From: Matti Paksula Date: Tue, 9 Jan 2018 10:55:36 +0200 Subject: [PATCH] space before $ --- docs/concepts/configuration/assign-pod-node.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/configuration/assign-pod-node.md b/docs/concepts/configuration/assign-pod-node.md index df6ace536b..55e8190fcb 100644 --- a/docs/concepts/configuration/assign-pod-node.md +++ b/docs/concepts/configuration/assign-pod-node.md @@ -296,7 +296,7 @@ If we create the above two deployments, our three node cluster should look like As you can see, all the 3 replicas of the `web-server` are automatically co-located with the cache as expected. ``` -$kubectl get pods -o wide +$ kubectl get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE redis-cache-1450370735-6dzlj 1/1 Running 0 8m 10.192.4.2 kube-node-3 redis-cache-1450370735-j2j96 1/1 Running 0 8m 10.192.2.2 kube-node-1