Remove data-lang for command outputs
This commit is contained in:
+1
-1
@@ -115,7 +115,7 @@ kubectl config --kubeconfig=config-demo view
|
||||
|
||||
The output shows the two clusters, two users, and three contexts:
|
||||
|
||||
```shell
|
||||
```yaml
|
||||
apiVersion: v1
|
||||
clusters:
|
||||
- cluster:
|
||||
|
||||
@@ -89,7 +89,7 @@ kubectl get persistentvolumeclaims --namespace=quota-object-example
|
||||
|
||||
The output shows that the PersistentVolumeClaim exists and has status Pending:
|
||||
|
||||
```shell
|
||||
```
|
||||
NAME STATUS
|
||||
pvc-quota-demo Pending
|
||||
```
|
||||
|
||||
@@ -171,7 +171,7 @@ kubectl get pod memory-demo-2 --output=yaml --namespace=mem-example
|
||||
|
||||
The output shows that the Container was killed because it is out of memory (OOM):
|
||||
|
||||
```shell
|
||||
```yaml
|
||||
lastState:
|
||||
terminated:
|
||||
containerID: 65183c1877aaec2e8427bc95609cc52677a454b56fcb24340dbd22917c23b10f
|
||||
@@ -278,7 +278,7 @@ kubectl describe pod memory-demo-3 --namespace=mem-example
|
||||
|
||||
The output shows that the Container cannot be scheduled because of insufficient memory on the Nodes:
|
||||
|
||||
```shell
|
||||
```
|
||||
Events:
|
||||
... Reason Message
|
||||
------ -------
|
||||
@@ -291,8 +291,8 @@ The memory resource is measured in bytes. You can express memory as a plain inte
|
||||
fixed-point integer with one of these suffixes: E, P, T, G, M, K, Ei, Pi, Ti, Gi, Mi, Ki.
|
||||
For example, the following represent approximately the same value:
|
||||
|
||||
```shell
|
||||
128974848, 129e6, 129M , 123Mi
|
||||
```
|
||||
128974848, 129e6, 129M, 123Mi
|
||||
```
|
||||
|
||||
Delete your Pod:
|
||||
|
||||
@@ -548,7 +548,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-env-var-valu
|
||||
|
||||
produces the following output in the `test-container` container:
|
||||
|
||||
```shell
|
||||
```
|
||||
very charm
|
||||
```
|
||||
|
||||
@@ -582,7 +582,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-volume.yaml
|
||||
|
||||
When the pod runs, the command `ls /etc/config/` produces the output below:
|
||||
|
||||
```shell
|
||||
```
|
||||
SPECIAL_LEVEL
|
||||
SPECIAL_TYPE
|
||||
```
|
||||
@@ -610,7 +610,7 @@ kubectl create -f https://kubernetes.io/examples/pods/pod-configmap-volume-speci
|
||||
|
||||
When the pod runs, the command `cat /etc/config/keys` produces the output below:
|
||||
|
||||
```shell
|
||||
```
|
||||
very
|
||||
```
|
||||
|
||||
|
||||
@@ -57,7 +57,7 @@ echo $env:USERNAME
|
||||
|
||||
The output should be:
|
||||
|
||||
```shell
|
||||
```
|
||||
ContainerUser
|
||||
```
|
||||
|
||||
@@ -97,7 +97,7 @@ echo $env:USERNAME
|
||||
|
||||
The output should be:
|
||||
|
||||
```shell
|
||||
```
|
||||
ContainerAdministrator
|
||||
```
|
||||
|
||||
|
||||
+1
-1
@@ -69,7 +69,7 @@ kubectl logs kubernetes-downwardapi-volume-example
|
||||
|
||||
The output shows the contents of the `labels` file and the `annotations` file:
|
||||
|
||||
```shell
|
||||
```
|
||||
cluster="test-cluster1"
|
||||
rack="rack-22"
|
||||
zone="us-est-coast"
|
||||
|
||||
@@ -79,7 +79,7 @@ kubectl apply -f https://k8s.io/examples/controllers/fluentd-daemonset.yaml --dr
|
||||
|
||||
The output from both commands should be:
|
||||
|
||||
```shell
|
||||
```
|
||||
RollingUpdate
|
||||
```
|
||||
|
||||
|
||||
@@ -82,7 +82,7 @@ kubectl get deployment patch-demo --output yaml
|
||||
|
||||
The output shows that the PodSpec in the Deployment has two Containers:
|
||||
|
||||
```shell
|
||||
```yaml
|
||||
containers:
|
||||
- image: redis
|
||||
imagePullPolicy: Always
|
||||
@@ -309,7 +309,7 @@ kubectl patch deployment retainkeys-demo --type merge --patch-file patch-file-no
|
||||
|
||||
In the output, you can see that it is not possible to set `type` as `Recreate` when a value is defined for `spec.strategy.rollingUpdate`:
|
||||
|
||||
```shell
|
||||
```
|
||||
The Deployment "retainkeys-demo" is invalid: spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate'
|
||||
```
|
||||
|
||||
@@ -341,7 +341,7 @@ kubectl get deployment retainkeys-demo --output yaml
|
||||
|
||||
The output shows that the strategy object in the Deployment does not contain the `rollingUpdate` key anymore:
|
||||
|
||||
```shell
|
||||
```yaml
|
||||
spec:
|
||||
strategy:
|
||||
type: Recreate
|
||||
|
||||
Reference in New Issue
Block a user