Update podpreset.md
parent
7df8556653
commit
4c347ea69d
|
@ -31,7 +31,7 @@ kubectl create -f https://k8s.io/docs/tasks/inject-data-application/podpreset-pr
|
|||
Examine the created PodPreset:
|
||||
|
||||
```shell
|
||||
kubectl get podpreset
|
||||
$ kubectl get podpreset
|
||||
NAME AGE
|
||||
allow-database 1m
|
||||
```
|
||||
|
@ -43,13 +43,13 @@ The new PodPreset will act upon any pod that has label `role: frontend`.
|
|||
Create a pod:
|
||||
|
||||
```shell
|
||||
kubectl create -f https://k8s.io/docs/tasks/inject-data-application/podpreset-pod.yaml
|
||||
$ kubectl create -f https://k8s.io/docs/tasks/inject-data-application/podpreset-pod.yaml
|
||||
```
|
||||
|
||||
List the running Pods:
|
||||
|
||||
```shell
|
||||
kubectl get pods
|
||||
$ kubectl get pods
|
||||
NAME READY STATUS RESTARTS AGE
|
||||
website 1/1 Running 0 4m
|
||||
```
|
||||
|
@ -61,7 +61,7 @@ website 1/1 Running 0 4m
|
|||
To see above output, run the following command:
|
||||
|
||||
```shell
|
||||
kubectl get pod website -o yaml
|
||||
$ kubectl get pod website -o yaml
|
||||
```
|
||||
|
||||
### Pod Spec with `ConfigMap` Example
|
||||
|
@ -145,7 +145,7 @@ when there is a conflict.
|
|||
|
||||
**If we run `kubectl describe...` we can see the event:**
|
||||
|
||||
```
|
||||
```shell
|
||||
$ kubectl describe ...
|
||||
....
|
||||
Events:
|
||||
|
|
Loading…
Reference in New Issue