Breaking News: Grepper is joining You.com. Read the official announcement!
Check it out

Pausing and Resuming a rollout of a Deployment

Sumit Rawal answered on May 6, 2023 Popularity 1/10 Helpfulness 1/10

Contents


More Related Answers


Pausing and Resuming a rollout of a Deployment

0

When you update a Deployment, or plan to, you can pause rollouts for that Deployment before you trigger

one or more updates. When you're ready to apply those changes, you resume rollouts for the Deployment.

This approach allows you to apply multiple fixes in between pausing and resuming without triggering

unnecessary rollouts

1. Get the Deployment details:

kubectl get deploy

2. Pause by running the following command:

kubectl rollout pause deployment/ubuntu-deployment

3. Then update the image of the Deployment:

kubectl set image deployment.v1.apps/ubuntu-deployment ubuntu=ubuntu:16.04

4. Notice that no new rollout started:

kubectl rollout history deployment/ubuntu-deployment

5. Get the rollout status to verify that the existing ReplicaSet has not changed: kubectl get rs

6. You can make as many updates as you wish, for example, update the resources that will be used:

kubectl set resources deployment/ubuntu-deployment -c=ubuntu--limits=cpu=200m,memory=512Mi

Eventually, resume the Deployment rollout and observe a new ReplicaSet coming up with all the new

updates:

7.

kubectl rollout resume deployment/ubuntu-deployment

8. Watch the status of the rollout until it's done.

kubectl get rs -w 

Popularity 1/10 Helpfulness 1/10 Language whatever
Source: Grepper
Link to this answer
Share Copy Link
Contributed on May 06 2023
Sumit Rawal
0 Answers  Avg Quality 2/10


X

Continue with Google

By continuing, I agree that I have read and agree to Greppers's Terms of Service and Privacy Policy.
X
Grepper Account Login Required

Oops, You will need to install Grepper and log-in to perform this action.