Fix leading spaces in kubectl commands

This is causing bash/zsh shells to not to record the executed command in the
history. See this link for details: https://unix.stackexchange.com/questions/115917/why-is-bash-not-storing-commands-that-start-with-spaces

Signed-off-by: Ahmet Alp Balkan <ahmetb@google.com>

docs/tutorials/object-management-kubectl/declarative-object-management-configuration.md

@@ -894,7 +894,7 @@ configuration involves several manual steps:
 
 1. Export the live object to a local configuration file:
 
-        kubectl get <kind>/<name> -o yaml --export > <kind>_<name>.yaml
+       kubectl get <kind>/<name> -o yaml --export > <kind>_<name>.yaml
 
 1. Manually remove the `status` field from the configuration file.
 
@@ -903,7 +903,7 @@ configuration involves several manual steps:
 
 1. Set the `kubectl.kubernetes.io/last-applied-configuration` annotation on the object:
 
-        kubectl replace --save-config -f <kind>_<name>.yaml
+       kubectl replace --save-config -f <kind>_<name>.yaml
 
 1. Change processes to use `kubectl apply` for managing the object exclusively.
 
@@ -915,7 +915,7 @@ TODO(pwittrock): Why doesn't export remove the status field?  Seems like it shou
 
 1. Set the `kubectl.kubernetes.io/last-applied-configuration` annotation on the object:
 
-        kubectl replace --save-config -f <kind>_<name>.yaml
+       kubectl replace --save-config -f <kind>_<name>.yaml
 
 1. Change processes to use `kubectl apply` for managing the object exclusively.
 

docs/tutorials/object-management-kubectl/imperative-object-management-configuration.md

@@ -97,13 +97,13 @@ several manual steps.
 
 1. Export the live object to a local object configuration file:
 
-        kubectl get <kind>/<name> -o yaml --export > <kind>_<name>.yaml
+       kubectl get <kind>/<name> -o yaml --export > <kind>_<name>.yaml
 
 1. Manually remove the status field from the object configuration file.
 
 1. For subsequent object management, use `replace` exclusively.
 
-        kubectl replace -f <kind>_<name>.yaml
+       kubectl replace -f <kind>_<name>.yaml
 
 
 ## Defining controller selectors and PodTemplate labels

docs/tutorials/stateless-application/expose-external-ip-address.md

@@ -40,7 +40,7 @@ external IP address.
 
 1. Run a Hello World application in your cluster:
 
-        kubectl run hello-world --replicas=5 --labels="run=load-balancer-example" --image=gcr.io/google-samples/node-hello:1.0  --port=8080
+       kubectl run hello-world --replicas=5 --labels="run=load-balancer-example" --image=gcr.io/google-samples/node-hello:1.0  --port=8080
 
     The preceding command creates a
     [Deployment](/docs/concepts/workloads/controllers/deployment/)
@@ -52,21 +52,21 @@ external IP address.
 
 1. Display information about the Deployment:
 
-        kubectl get deployments hello-world
-        kubectl describe deployments hello-world
+       kubectl get deployments hello-world
+       kubectl describe deployments hello-world
 
 1. Display information about your ReplicaSet objects:
 
-        kubectl get replicasets
-        kubectl describe replicasets
+       kubectl get replicasets
+       kubectl describe replicasets
 
 1. Create a Service object that exposes the deployment:
 
-        kubectl expose deployment hello-world --type=LoadBalancer --name=my-service
+       kubectl expose deployment hello-world --type=LoadBalancer --name=my-service
 
 1. Display information about the Service:
 
-        kubectl get services my-service
+       kubectl get services my-service
 
     The output is similar to this:
 
@@ -78,7 +78,7 @@ external IP address.
 
 1. Display detailed information about the Service:
 
-        kubectl describe services my-service
+       kubectl describe services my-service
 
     The output is similar to this:
 
@@ -104,7 +104,7 @@ external IP address.
    addresses of the pods that are running the Hello World application. To
    verify these are pod addresses, enter this command:
 
-        kubectl get pods --output=wide
+       kubectl get pods --output=wide
 
     The output is similar to this: