Replace $ symbol in all english docs files

content/en/docs/concepts/cluster-administration/logging.md

@@ -35,14 +35,14 @@ a container that writes some text to standard output once per second.
 To run this pod, use the following command:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
+kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
 pod/counter created
 ```
 
 To fetch the logs, use the `kubectl logs` command, as follows:
 
 ```shell
-$ kubectl logs counter
+kubectl logs counter
 0: Mon Jan  1 00:00:00 UTC 2001
 1: Mon Jan  1 00:00:01 UTC 2001
 2: Mon Jan  1 00:00:02 UTC 2001
@@ -178,15 +178,15 @@ Now when you run this pod, you can access each log stream separately by
 running the following commands:
 
 ```shell
-$ kubectl logs counter count-log-1
+kubectl logs counter count-log-1
 0: Mon Jan  1 00:00:00 UTC 2001
 1: Mon Jan  1 00:00:01 UTC 2001
 2: Mon Jan  1 00:00:02 UTC 2001
 ...
 ```
 
 ```shell
-$ kubectl logs counter count-log-2
+kubectl logs counter count-log-2
 Mon Jan  1 00:00:00 UTC 2001 INFO 0
 Mon Jan  1 00:00:01 UTC 2001 INFO 1
 Mon Jan  1 00:00:02 UTC 2001 INFO 2

content/en/docs/concepts/cluster-administration/manage-deployment.md

@@ -26,7 +26,7 @@ Many applications require multiple resources to be created, such as a Deployment
 Multiple resources can be created the same way as a single resource:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/application/nginx-app.yaml
+kubectl create -f https://k8s.io/examples/application/nginx-app.yaml
 service/my-nginx-svc created
 deployment.apps/my-nginx created
 ```
@@ -36,13 +36,13 @@ The resources will be created in the order they appear in the file. Therefore, i
 `kubectl create` also accepts multiple `-f` arguments:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/application/nginx/nginx-svc.yaml -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
+kubectl create -f https://k8s.io/examples/application/nginx/nginx-svc.yaml -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
 ```
 
 And a directory can be specified rather than or in addition to individual files:
 
 ```shell
-$ kubectl create -f https://k8s.io/examples/application/nginx/
+kubectl create -f https://k8s.io/examples/application/nginx/
 ```
 
 `kubectl` will read any files with suffixes `.yaml`, `.yml`, or `.json`.
@@ -52,7 +52,7 @@ It is a recommended practice to put resources related to the same microservice o
 A URL can also be specified as a configuration source, which is handy for deploying directly from configuration files checked into github:
 
 ```shell
-$ kubectl create -f https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/application/nginx/nginx-deployment.yaml
+kubectl create -f https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/application/nginx/nginx-deployment.yaml
 deployment.apps/my-nginx created
 ```
 
@@ -61,29 +61,29 @@ deployment.apps/my-nginx created
 Resource creation isn't the only operation that `kubectl` can perform in bulk. It can also extract resource names from configuration files in order to perform other operations, in particular to delete the same resources you created:
 
 ```shell
-$ kubectl delete -f https://k8s.io/examples/application/nginx-app.yaml
+kubectl delete -f https://k8s.io/examples/application/nginx-app.yaml
 deployment.apps "my-nginx" deleted
 service "my-nginx-svc" deleted
 ```
 
 In the case of just two resources, it's also easy to specify both on the command line using the resource/name syntax:
 
 ```shell
-$ kubectl delete deployments/my-nginx services/my-nginx-svc
+kubectl delete deployments/my-nginx services/my-nginx-svc
 ```
 
 For larger numbers of resources, you'll find it easier to specify the selector (label query) specified using `-l` or `--selector`, to filter resources by their labels:
 
 ```shell
-$ kubectl delete deployment,services -l app=nginx
+kubectl delete deployment,services -l app=nginx
 deployment.apps "my-nginx" deleted
 service "my-nginx-svc" deleted
 ```
 
 Because `kubectl` outputs resource names in the same syntax it accepts, it's easy to chain operations using `$()` or `xargs`:
 
 ```shell
-$ kubectl get $(kubectl create -f docs/concepts/cluster-administration/nginx/ -o name | grep service)
+kubectl get $(kubectl create -f docs/concepts/cluster-administration/nginx/ -o name | grep service)
 NAME           TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)      AGE
 my-nginx-svc   LoadBalancer   10.0.0.208   <pending>     80/TCP       0s
 ```
@@ -108,14 +108,14 @@ project/k8s/development
 By default, performing a bulk operation on `project/k8s/development` will stop at the first level of the directory, not processing any subdirectories. If we had tried to create the resources in this directory using the following command, we would have encountered an error:
 
 ```shell
-$ kubectl create -f project/k8s/development
+kubectl create -f project/k8s/development
 error: you must provide one or more resources by argument or filename (.json|.yaml|.yml|stdin)
 ```
 
 Instead, specify the `--recursive` or `-R` flag with the `--filename,-f` flag as such:
 
 ```shell
-$ kubectl create -f project/k8s/development --recursive
+kubectl create -f project/k8s/development --recursive
 configmap/my-config created
 deployment.apps/my-deployment created
 persistentvolumeclaim/my-pvc created
@@ -126,7 +126,7 @@ The `--recursive` flag works with any operation that accepts the `--filename,-f`
 The `--recursive` flag also works when multiple `-f` arguments are provided:
 
 ```shell
-$ kubectl create -f project/k8s/namespaces -f project/k8s/development --recursive
+kubectl create -f project/k8s/namespaces -f project/k8s/development --recursive
 namespace/development created
 namespace/staging created
 configmap/my-config created
@@ -169,8 +169,8 @@ and
 The labels allow us to slice and dice our resources along any dimension specified by a label:
 
 ```shell
-$ kubectl create -f examples/guestbook/all-in-one/guestbook-all-in-one.yaml
-$ kubectl get pods -Lapp -Ltier -Lrole
+kubectl create -f examples/guestbook/all-in-one/guestbook-all-in-one.yaml
+kubectl get pods -Lapp -Ltier -Lrole
 NAME                           READY     STATUS    RESTARTS   AGE       APP         TIER       ROLE
 guestbook-fe-4nlpb             1/1       Running   0          1m        guestbook   frontend   <none>
 guestbook-fe-ght6d             1/1       Running   0          1m        guestbook   frontend   <none>
@@ -180,7 +180,7 @@ guestbook-redis-slave-2q2yf    1/1       Running   0          1m        guestboo
 guestbook-redis-slave-qgazl    1/1       Running   0          1m        guestbook   backend    slave
 my-nginx-divi2                 1/1       Running   0          29m       nginx       <none>     <none>
 my-nginx-o0ef1                 1/1       Running   0          29m       nginx       <none>     <none>
-$ kubectl get pods -lapp=guestbook,role=slave
+kubectl get pods -lapp=guestbook,role=slave
 NAME                          READY     STATUS    RESTARTS   AGE
 guestbook-redis-slave-2q2yf   1/1       Running   0          3m
 guestbook-redis-slave-qgazl   1/1       Running   0          3m
@@ -240,7 +240,7 @@ Sometimes existing pods and other resources need to be relabeled before creating
 For example, if you want to label all your nginx pods as frontend tier, simply run:
 
 ```shell
-$ kubectl label pods -l app=nginx tier=fe
+kubectl label pods -l app=nginx tier=fe
 pod/my-nginx-2035384211-j5fhi labeled
 pod/my-nginx-2035384211-u2c7e labeled
 pod/my-nginx-2035384211-u3t6x labeled
@@ -250,7 +250,7 @@ This first filters all pods with the label "app=nginx", and then labels them wit
 To see the pods you just labeled, run:
 
 ```shell
-$ kubectl get pods -l app=nginx -L tier
+kubectl get pods -l app=nginx -L tier
 NAME                        READY     STATUS    RESTARTS   AGE       TIER
 my-nginx-2035384211-j5fhi   1/1       Running   0          23m       fe
 my-nginx-2035384211-u2c7e   1/1       Running   0          23m       fe
@@ -266,8 +266,8 @@ For more information, please see [labels](/docs/concepts/overview/working-with-o
 Sometimes you would want to attach annotations to resources. Annotations are arbitrary non-identifying metadata for retrieval by API clients such as tools, libraries, etc. This can be done with `kubectl annotate`. For example:
 
 ```shell
-$ kubectl annotate pods my-nginx-v4-9gw19 description='my frontend running nginx'
-$ kubectl get pods my-nginx-v4-9gw19 -o yaml
+kubectl annotate pods my-nginx-v4-9gw19 description='my frontend running nginx'
+kubectl get pods my-nginx-v4-9gw19 -o yaml
 apiversion: v1
 kind: pod
 metadata:
@@ -283,22 +283,22 @@ For more information, please see [annotations](/docs/concepts/overview/working-w
 When load on your application grows or shrinks, it's easy to scale with `kubectl`. For instance, to decrease the number of nginx replicas from 3 to 1, do:
 
 ```shell
-$ kubectl scale deployment/my-nginx --replicas=1
+kubectl scale deployment/my-nginx --replicas=1
 deployment.extensions/my-nginx scaled
 ```
 
 Now you only have one pod managed by the deployment.
 
 ```shell
-$ kubectl get pods -l app=nginx
+kubectl get pods -l app=nginx
 NAME                        READY     STATUS    RESTARTS   AGE
 my-nginx-2035384211-j5fhi   1/1       Running   0          30m
 ```
 
 To have the system automatically choose the number of nginx replicas as needed, ranging from 1 to 3, do:
 
 ```shell
-$ kubectl autoscale deployment/my-nginx --min=1 --max=3
+kubectl autoscale deployment/my-nginx --min=1 --max=3
 horizontalpodautoscaler.autoscaling/my-nginx autoscaled
 ```
 
@@ -320,7 +320,7 @@ Then, you can use [`kubectl apply`](/docs/reference/generated/kubectl/kubectl-co
 This command will compare the version of the configuration that you're pushing with the previous version and apply the changes you've made, without overwriting any automated changes to properties you haven't specified.
 
 ```shell
-$ kubectl apply -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
+kubectl apply -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
 deployment.apps/my-nginx configured
 ```
 
@@ -339,16 +339,16 @@ To use apply, always create resource initially with either `kubectl apply` or `k
 Alternatively, you may also update resources with `kubectl edit`:
 
 ```shell
-$ kubectl edit deployment/my-nginx
+kubectl edit deployment/my-nginx
 ```
 
 This is equivalent to first `get` the resource, edit it in text editor, and then `apply` the resource with the updated version:
 
 ```shell
-$ kubectl get deployment my-nginx -o yaml > /tmp/nginx.yaml
+kubectl get deployment my-nginx -o yaml > /tmp/nginx.yaml
 $ vi /tmp/nginx.yaml
 # do some edit, and then save the file
-$ kubectl apply -f /tmp/nginx.yaml
+kubectl apply -f /tmp/nginx.yaml
 deployment.apps/my-nginx configured
 $ rm /tmp/nginx.yaml
 ```
@@ -370,7 +370,7 @@ and
 In some cases, you may need to update resource fields that cannot be updated once initialized, or you may just want to make a recursive change immediately, such as to fix broken pods created by a Deployment. To change such fields, use `replace --force`, which deletes and re-creates the resource. In this case, you can simply modify your original configuration file:
 
 ```shell
-$ kubectl replace -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml --force
+kubectl replace -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml --force
 deployment.apps/my-nginx deleted
 deployment.apps/my-nginx replaced
 ```
@@ -385,14 +385,14 @@ you should read [how to use `kubectl rolling-update`](/docs/tasks/run-applicatio
 Let's say you were running version 1.7.9 of nginx:
 
 ```shell
-$ kubectl run my-nginx --image=nginx:1.7.9 --replicas=3
+kubectl run my-nginx --image=nginx:1.7.9 --replicas=3
 deployment.apps/my-nginx created
 ```
 
 To update to version 1.9.1, simply change `.spec.template.spec.containers[0].image` from `nginx:1.7.9` to `nginx:1.9.1`, with the kubectl commands we learned above.
 
 ```shell
-$ kubectl edit deployment/my-nginx
+kubectl edit deployment/my-nginx
 ```
 
 That's it! The Deployment will declaratively update the deployed nginx application progressively behind the scene. It ensures that only a certain number of old replicas may be down while they are being updated, and only a certain number of new replicas may be created above the desired number of pods. To learn more details about it, visit [Deployment page](/docs/concepts/workloads/controllers/deployment/).

content/en/docs/concepts/configuration/assign-pod-node.md

@@ -339,7 +339,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

content/en/docs/concepts/configuration/manage-compute-resources-container.md

@@ -189,7 +189,7 @@ unscheduled until a place can be found. An event is produced each time the
 scheduler fails to find a place for the Pod, like this:
 
 ```shell
-$ kubectl describe pod frontend | grep -A 3 Events
+kubectl describe pod frontend | grep -A 3 Events
 Events:
   FirstSeen LastSeen   Count  From          Subobject   PathReason      Message
   36s   5s     6      {scheduler }              FailedScheduling  Failed for reason PodExceedsFreeCPU and possibly others
@@ -210,7 +210,7 @@ You can check node capacities and amounts allocated with the
 `kubectl describe nodes` command. For example:
 
 ```shell
-$ kubectl describe nodes e2e-test-minion-group-4lw4
+kubectl describe nodes e2e-test-minion-group-4lw4
 Name:            e2e-test-minion-group-4lw4
 [ ... lines removed for clarity ...]
 Capacity:

content/en/docs/concepts/configuration/secret.md

@@ -70,18 +70,18 @@ packages these files into a Secret and creates
 the object on the Apiserver.
 
 ```shell
-$ kubectl create secret generic db-user-pass --from-file=./username.txt --from-file=./password.txt
+kubectl create secret generic db-user-pass --from-file=./username.txt --from-file=./password.txt
 secret "db-user-pass" created
 ```
 
 You can check that the secret was created like this:
 
 ```shell
-$ kubectl get secrets
+kubectl get secrets
 NAME                  TYPE                                  DATA      AGE
 db-user-pass          Opaque                                2         51s
 
-$ kubectl describe secrets/db-user-pass
+kubectl describe secrets/db-user-pass
 Name:            db-user-pass
 Namespace:       default
 Labels:          <none>
@@ -139,7 +139,7 @@ data:
 Now create the Secret using [`kubectl create`](/docs/reference/generated/kubectl/kubectl-commands#create):
 
 ```shell
-$ kubectl create -f ./secret.yaml
+kubectl create -f ./secret.yaml
 secret "mysecret" created
 ```
 
@@ -250,7 +250,7 @@ the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if
 Secrets can be retrieved via the `kubectl get secret` command. For example, to retrieve the secret created in the previous section:
 
 ```shell
-$ kubectl get secret mysecret -o yaml
+kubectl get secret mysecret -o yaml
 apiVersion: v1
 data:
   username: YWRtaW4=
@@ -569,7 +569,7 @@ invalid keys that were skipped. The example shows a pod which refers to the
 default/mysecret that contains 2 invalid keys, 1badkey and 2alsobad.
 
 ```shell
-$ kubectl get events
+kubectl get events
 LASTSEEN   FIRSTSEEN   COUNT     NAME            KIND      SUBOBJECT                         TYPE      REASON
 0s         0s          1         dapi-test-pod   Pod                                         Warning   InvalidEnvironmentVariableNames   kubelet, 127.0.0.1      Keys [1badkey, 2alsobad] from the EnvFrom secret default/mysecret were skipped since they are considered invalid environment variable names.
 ```
@@ -592,7 +592,7 @@ start until all the pod's volumes are mounted.
 Create a secret containing some ssh keys:
 
 ```shell
-$ kubectl create secret generic ssh-key-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub
+kubectl create secret generic ssh-key-secret --from-file=ssh-privatekey=/path/to/.ssh/id_rsa --from-file=ssh-publickey=/path/to/.ssh/id_rsa.pub
 ```
 
 {{< caution >}}
@@ -642,9 +642,9 @@ credentials.
 Make the secrets:
 
 ```shell
-$ kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
+kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
 secret "prod-db-secret" created
-$ kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
+kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
 secret "test-db-secret" created
 ```
 {{< note >}}