@@ -97,7 +97,7 @@ Follow the steps given below to create the above Deployment:
97
97
98
98
Notice how the number of desired replicas is 3 according to ` .spec.replicas ` field.
99
99
100
- 3 . To see the Deployment rollout status, run ` kubectl rollout status deployment.v1.apps /nginx-deployment ` .
100
+ 3 . To see the Deployment rollout status, run ` kubectl rollout status deployment/nginx-deployment ` .
101
101
102
102
The output is similar to:
103
103
```
@@ -196,7 +196,7 @@ Follow the steps given below to update your Deployment:
196
196
2. To see the rollout status, run:
197
197
198
198
` ` ` shell
199
- kubectl rollout status deployment.v1.apps /nginx-deployment
199
+ kubectl rollout status deployment/nginx-deployment
200
200
` ` `
201
201
202
202
The output is similar to this:
@@ -374,7 +374,7 @@ rolled back.
374
374
* The rollout gets stuck. You can verify it by checking the rollout status:
375
375
376
376
` ` ` shell
377
- kubectl rollout status deployment.v1.apps /nginx-deployment
377
+ kubectl rollout status deployment/nginx-deployment
378
378
` ` `
379
379
380
380
The output is similar to this:
@@ -852,7 +852,7 @@ You can check if a Deployment has completed by using `kubectl rollout status`. I
852
852
successfully, ` kubectl rollout status` returns a zero exit code.
853
853
854
854
` ` ` shell
855
- kubectl rollout status deployment.v1.apps /nginx-deployment
855
+ kubectl rollout status deployment/nginx-deployment
856
856
` ` `
857
857
The output is similar to this:
858
858
` ` `
@@ -999,7 +999,7 @@ You can check if a Deployment has failed to progress by using `kubectl rollout s
999
999
returns a non-zero exit code if the Deployment has exceeded the progression deadline.
1000
1000
1001
1001
` ` ` shell
1002
- kubectl rollout status deployment.v1.apps /nginx-deployment
1002
+ kubectl rollout status deployment/nginx-deployment
1003
1003
` ` `
1004
1004
The output is similar to this:
1005
1005
` ` `
0 commit comments