@@ -84,7 +84,7 @@ Follow the steps given below to create the above Deployment:
84
84
2 . Run ` kubectl get deployments ` to check if the Deployment was created.
85
85
86
86
If the Deployment is still being created, the output is similar to the following:
87
- ``` shell
87
+ ```
88
88
NAME READY UP-TO-DATE AVAILABLE AGE
89
89
nginx-deployment 0/3 0 0 1s
90
90
```
@@ -100,21 +100,21 @@ Follow the steps given below to create the above Deployment:
100
100
3 . To see the Deployment rollout status, run ` kubectl rollout status deployment.v1.apps/nginx-deployment ` .
101
101
102
102
The output is similar to:
103
- ``` shell
103
+ ```
104
104
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
105
105
deployment.apps/nginx-deployment successfully rolled out
106
106
```
107
107
108
108
4 . Run the ` kubectl get deployments ` again a few seconds later.
109
109
The output is similar to this:
110
- ``` shell
110
+ ```
111
111
NAME READY UP-TO-DATE AVAILABLE AGE
112
112
nginx-deployment 3/3 3 3 18s
113
113
```
114
114
Notice that the Deployment has created all three replicas, and all replicas are up-to-date (they contain the latest Pod template) and available.
115
115
116
116
5 . To see the ReplicaSet (` rs ` ) created by the Deployment, run ` kubectl get rs ` . The output is similar to this:
117
- ``` shell
117
+ ```
118
118
NAME DESIRED CURRENT READY AGE
119
119
nginx-deployment-75675f5897 3 3 3 18s
120
120
```
@@ -131,7 +131,7 @@ Follow the steps given below to create the above Deployment:
131
131
132
132
6 . To see the labels automatically generated for each Pod, run ` kubectl get pods --show-labels ` .
133
133
The output is similar to:
134
- ``` shell
134
+ ```
135
135
NAME READY STATUS RESTARTS AGE LABELS
136
136
nginx-deployment-75675f5897-7ci7o 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
137
137
nginx-deployment-75675f5897-kzszj 1/1 Running 0 18s app=nginx,pod-template-hash=3123191453
0 commit comments