Skip to content

Commit dd56387

Browse files
DanyC97DanyC97
committed
Replace $ symbol in all english docs files
1 parent 6644ae9 commit dd56387

42 files changed

Lines changed: 347 additions & 347 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -35,14 +35,14 @@ a container that writes some text to standard output once per second.
3535
To run this pod, use the following command:
3636

3737
```shell
38-
$ kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
38+
kubectl create -f https://k8s.io/examples/debug/counter-pod.yaml
3939
pod/counter created
4040
```
4141

4242
To fetch the logs, use the `kubectl logs` command, as follows:
4343

4444
```shell
45-
$ kubectl logs counter
45+
kubectl logs counter
4646
0: Mon Jan 1 00:00:00 UTC 2001
4747
1: Mon Jan 1 00:00:01 UTC 2001
4848
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
178178
running the following commands:
179179

180180
```shell
181-
$ kubectl logs counter count-log-1
181+
kubectl logs counter count-log-1
182182
0: Mon Jan 1 00:00:00 UTC 2001
183183
1: Mon Jan 1 00:00:01 UTC 2001
184184
2: Mon Jan 1 00:00:02 UTC 2001
185185
...
186186
```
187187

188188
```shell
189-
$ kubectl logs counter count-log-2
189+
kubectl logs counter count-log-2
190190
Mon Jan 1 00:00:00 UTC 2001 INFO 0
191191
Mon Jan 1 00:00:01 UTC 2001 INFO 1
192192
Mon Jan 1 00:00:02 UTC 2001 INFO 2

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

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Many applications require multiple resources to be created, such as a Deployment
2626
Multiple resources can be created the same way as a single resource:
2727

2828
```shell
29-
$ kubectl create -f https://k8s.io/examples/application/nginx-app.yaml
29+
kubectl create -f https://k8s.io/examples/application/nginx-app.yaml
3030
service/my-nginx-svc created
3131
deployment.apps/my-nginx created
3232
```
@@ -36,13 +36,13 @@ The resources will be created in the order they appear in the file. Therefore, i
3636
`kubectl create` also accepts multiple `-f` arguments:
3737

3838
```shell
39-
$ kubectl create -f https://k8s.io/examples/application/nginx/nginx-svc.yaml -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
39+
kubectl create -f https://k8s.io/examples/application/nginx/nginx-svc.yaml -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
4040
```
4141

4242
And a directory can be specified rather than or in addition to individual files:
4343

4444
```shell
45-
$ kubectl create -f https://k8s.io/examples/application/nginx/
45+
kubectl create -f https://k8s.io/examples/application/nginx/
4646
```
4747

4848
`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
5252
A URL can also be specified as a configuration source, which is handy for deploying directly from configuration files checked into github:
5353

5454
```shell
55-
$ kubectl create -f https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/application/nginx/nginx-deployment.yaml
55+
kubectl create -f https://raw.githubusercontent.com/kubernetes/website/master/content/en/examples/application/nginx/nginx-deployment.yaml
5656
deployment.apps/my-nginx created
5757
```
5858

@@ -61,29 +61,29 @@ deployment.apps/my-nginx created
6161
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:
6262

6363
```shell
64-
$ kubectl delete -f https://k8s.io/examples/application/nginx-app.yaml
64+
kubectl delete -f https://k8s.io/examples/application/nginx-app.yaml
6565
deployment.apps "my-nginx" deleted
6666
service "my-nginx-svc" deleted
6767
```
6868

6969
In the case of just two resources, it's also easy to specify both on the command line using the resource/name syntax:
7070

7171
```shell
72-
$ kubectl delete deployments/my-nginx services/my-nginx-svc
72+
kubectl delete deployments/my-nginx services/my-nginx-svc
7373
```
7474

7575
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:
7676

7777
```shell
78-
$ kubectl delete deployment,services -l app=nginx
78+
kubectl delete deployment,services -l app=nginx
7979
deployment.apps "my-nginx" deleted
8080
service "my-nginx-svc" deleted
8181
```
8282

8383
Because `kubectl` outputs resource names in the same syntax it accepts, it's easy to chain operations using `$()` or `xargs`:
8484

8585
```shell
86-
$ kubectl get $(kubectl create -f docs/concepts/cluster-administration/nginx/ -o name | grep service)
86+
kubectl get $(kubectl create -f docs/concepts/cluster-administration/nginx/ -o name | grep service)
8787
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
8888
my-nginx-svc LoadBalancer 10.0.0.208 <pending> 80/TCP 0s
8989
```
@@ -108,14 +108,14 @@ project/k8s/development
108108
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:
109109

110110
```shell
111-
$ kubectl create -f project/k8s/development
111+
kubectl create -f project/k8s/development
112112
error: you must provide one or more resources by argument or filename (.json|.yaml|.yml|stdin)
113113
```
114114

115115
Instead, specify the `--recursive` or `-R` flag with the `--filename,-f` flag as such:
116116

117117
```shell
118-
$ kubectl create -f project/k8s/development --recursive
118+
kubectl create -f project/k8s/development --recursive
119119
configmap/my-config created
120120
deployment.apps/my-deployment created
121121
persistentvolumeclaim/my-pvc created
@@ -126,7 +126,7 @@ The `--recursive` flag works with any operation that accepts the `--filename,-f`
126126
The `--recursive` flag also works when multiple `-f` arguments are provided:
127127

128128
```shell
129-
$ kubectl create -f project/k8s/namespaces -f project/k8s/development --recursive
129+
kubectl create -f project/k8s/namespaces -f project/k8s/development --recursive
130130
namespace/development created
131131
namespace/staging created
132132
configmap/my-config created
@@ -169,8 +169,8 @@ and
169169
The labels allow us to slice and dice our resources along any dimension specified by a label:
170170

171171
```shell
172-
$ kubectl create -f examples/guestbook/all-in-one/guestbook-all-in-one.yaml
173-
$ kubectl get pods -Lapp -Ltier -Lrole
172+
kubectl create -f examples/guestbook/all-in-one/guestbook-all-in-one.yaml
173+
kubectl get pods -Lapp -Ltier -Lrole
174174
NAME READY STATUS RESTARTS AGE APP TIER ROLE
175175
guestbook-fe-4nlpb 1/1 Running 0 1m guestbook frontend <none>
176176
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
180180
guestbook-redis-slave-qgazl 1/1 Running 0 1m guestbook backend slave
181181
my-nginx-divi2 1/1 Running 0 29m nginx <none> <none>
182182
my-nginx-o0ef1 1/1 Running 0 29m nginx <none> <none>
183-
$ kubectl get pods -lapp=guestbook,role=slave
183+
kubectl get pods -lapp=guestbook,role=slave
184184
NAME READY STATUS RESTARTS AGE
185185
guestbook-redis-slave-2q2yf 1/1 Running 0 3m
186186
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
240240
For example, if you want to label all your nginx pods as frontend tier, simply run:
241241

242242
```shell
243-
$ kubectl label pods -l app=nginx tier=fe
243+
kubectl label pods -l app=nginx tier=fe
244244
pod/my-nginx-2035384211-j5fhi labeled
245245
pod/my-nginx-2035384211-u2c7e labeled
246246
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
250250
To see the pods you just labeled, run:
251251

252252
```shell
253-
$ kubectl get pods -l app=nginx -L tier
253+
kubectl get pods -l app=nginx -L tier
254254
NAME READY STATUS RESTARTS AGE TIER
255255
my-nginx-2035384211-j5fhi 1/1 Running 0 23m fe
256256
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
266266
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:
267267

268268
```shell
269-
$ kubectl annotate pods my-nginx-v4-9gw19 description='my frontend running nginx'
270-
$ kubectl get pods my-nginx-v4-9gw19 -o yaml
269+
kubectl annotate pods my-nginx-v4-9gw19 description='my frontend running nginx'
270+
kubectl get pods my-nginx-v4-9gw19 -o yaml
271271
apiversion: v1
272272
kind: pod
273273
metadata:
@@ -283,22 +283,22 @@ For more information, please see [annotations](/docs/concepts/overview/working-w
283283
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:
284284

285285
```shell
286-
$ kubectl scale deployment/my-nginx --replicas=1
286+
kubectl scale deployment/my-nginx --replicas=1
287287
deployment.extensions/my-nginx scaled
288288
```
289289

290290
Now you only have one pod managed by the deployment.
291291

292292
```shell
293-
$ kubectl get pods -l app=nginx
293+
kubectl get pods -l app=nginx
294294
NAME READY STATUS RESTARTS AGE
295295
my-nginx-2035384211-j5fhi 1/1 Running 0 30m
296296
```
297297

298298
To have the system automatically choose the number of nginx replicas as needed, ranging from 1 to 3, do:
299299

300300
```shell
301-
$ kubectl autoscale deployment/my-nginx --min=1 --max=3
301+
kubectl autoscale deployment/my-nginx --min=1 --max=3
302302
horizontalpodautoscaler.autoscaling/my-nginx autoscaled
303303
```
304304

@@ -320,7 +320,7 @@ Then, you can use [`kubectl apply`](/docs/reference/generated/kubectl/kubectl-co
320320
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.
321321

322322
```shell
323-
$ kubectl apply -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
323+
kubectl apply -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml
324324
deployment.apps/my-nginx configured
325325
```
326326

@@ -339,16 +339,16 @@ To use apply, always create resource initially with either `kubectl apply` or `k
339339
Alternatively, you may also update resources with `kubectl edit`:
340340

341341
```shell
342-
$ kubectl edit deployment/my-nginx
342+
kubectl edit deployment/my-nginx
343343
```
344344

345345
This is equivalent to first `get` the resource, edit it in text editor, and then `apply` the resource with the updated version:
346346

347347
```shell
348-
$ kubectl get deployment my-nginx -o yaml > /tmp/nginx.yaml
348+
kubectl get deployment my-nginx -o yaml > /tmp/nginx.yaml
349349
$ vi /tmp/nginx.yaml
350350
# do some edit, and then save the file
351-
$ kubectl apply -f /tmp/nginx.yaml
351+
kubectl apply -f /tmp/nginx.yaml
352352
deployment.apps/my-nginx configured
353353
$ rm /tmp/nginx.yaml
354354
```
@@ -370,7 +370,7 @@ and
370370
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:
371371

372372
```shell
373-
$ kubectl replace -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml --force
373+
kubectl replace -f https://k8s.io/examples/application/nginx/nginx-deployment.yaml --force
374374
deployment.apps/my-nginx deleted
375375
deployment.apps/my-nginx replaced
376376
```
@@ -385,14 +385,14 @@ you should read [how to use `kubectl rolling-update`](/docs/tasks/run-applicatio
385385
Let's say you were running version 1.7.9 of nginx:
386386

387387
```shell
388-
$ kubectl run my-nginx --image=nginx:1.7.9 --replicas=3
388+
kubectl run my-nginx --image=nginx:1.7.9 --replicas=3
389389
deployment.apps/my-nginx created
390390
```
391391

392392
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.
393393

394394
```shell
395-
$ kubectl edit deployment/my-nginx
395+
kubectl edit deployment/my-nginx
396396
```
397397

398398
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‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -339,7 +339,7 @@ If we create the above two deployments, our three node cluster should look like
339339
As you can see, all the 3 replicas of the `web-server` are automatically co-located with the cache as expected.
340340

341341
```
342-
$ kubectl get pods -o wide
342+
kubectl get pods -o wide
343343
NAME READY STATUS RESTARTS AGE IP NODE
344344
redis-cache-1450370735-6dzlj 1/1 Running 0 8m 10.192.4.2 kube-node-3
345345
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‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ unscheduled until a place can be found. An event is produced each time the
189189
scheduler fails to find a place for the Pod, like this:
190190

191191
```shell
192-
$ kubectl describe pod frontend | grep -A 3 Events
192+
kubectl describe pod frontend | grep -A 3 Events
193193
Events:
194194
FirstSeen LastSeen Count From Subobject PathReason Message
195195
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
210210
`kubectl describe nodes` command. For example:
211211

212212
```shell
213-
$ kubectl describe nodes e2e-test-minion-group-4lw4
213+
kubectl describe nodes e2e-test-minion-group-4lw4
214214
Name: e2e-test-minion-group-4lw4
215215
[ ... lines removed for clarity ...]
216216
Capacity:

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -70,18 +70,18 @@ packages these files into a Secret and creates
7070
the object on the Apiserver.
7171

7272
```shell
73-
$ kubectl create secret generic db-user-pass --from-file=./username.txt --from-file=./password.txt
73+
kubectl create secret generic db-user-pass --from-file=./username.txt --from-file=./password.txt
7474
secret "db-user-pass" created
7575
```
7676

7777
You can check that the secret was created like this:
7878

7979
```shell
80-
$ kubectl get secrets
80+
kubectl get secrets
8181
NAME TYPE DATA AGE
8282
db-user-pass Opaque 2 51s
8383

84-
$ kubectl describe secrets/db-user-pass
84+
kubectl describe secrets/db-user-pass
8585
Name: db-user-pass
8686
Namespace: default
8787
Labels: <none>
@@ -139,7 +139,7 @@ data:
139139
Now create the Secret using [`kubectl create`](/docs/reference/generated/kubectl/kubectl-commands#create):
140140

141141
```shell
142-
$ kubectl create -f ./secret.yaml
142+
kubectl create -f ./secret.yaml
143143
secret "mysecret" created
144144
```
145145

@@ -250,7 +250,7 @@ the option `-w 0` to `base64` commands or the pipeline `base64 | tr -d '\n'` if
250250
Secrets can be retrieved via the `kubectl get secret` command. For example, to retrieve the secret created in the previous section:
251251

252252
```shell
253-
$ kubectl get secret mysecret -o yaml
253+
kubectl get secret mysecret -o yaml
254254
apiVersion: v1
255255
data:
256256
username: YWRtaW4=
@@ -569,7 +569,7 @@ invalid keys that were skipped. The example shows a pod which refers to the
569569
default/mysecret that contains 2 invalid keys, 1badkey and 2alsobad.
570570

571571
```shell
572-
$ kubectl get events
572+
kubectl get events
573573
LASTSEEN FIRSTSEEN COUNT NAME KIND SUBOBJECT TYPE REASON
574574
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.
575575
```
@@ -592,7 +592,7 @@ start until all the pod's volumes are mounted.
592592
Create a secret containing some ssh keys:
593593

594594
```shell
595-
$ 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
595+
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
596596
```
597597

598598
{{< caution >}}
@@ -642,9 +642,9 @@ credentials.
642642
Make the secrets:
643643

644644
```shell
645-
$ kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
645+
kubectl create secret generic prod-db-secret --from-literal=username=produser --from-literal=password=Y4nys7f11
646646
secret "prod-db-secret" created
647-
$ kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
647+
kubectl create secret generic test-db-secret --from-literal=username=testuser --from-literal=password=iluvtests
648648
secret "test-db-secret" created
649649
```
650650
{{< note >}}

0 commit comments

Comments
 (0)