Quick one about rollouts , so the idea is “ ” docker images to a new version “ ” disrupting services… that is relative and it is something i would like to investigate later on. update without But the general idea is , you have a deployment using a given version: So this deployment will create a with 3 containers running replicaset nginx:1.7.9. So the idea is that you change the image and update the deployment , this can be done in a few different ways , but one of them would be: kubectl set image deployment/nginx-deployment nginx=nginx:1.9.1 And what happens after is kind of interesting , if you run: kubectl describe deployments What you can see is how a new is created , and sequentially it gets incrased by 1 container , at the same time gets decreased by 1 , pretty smooth. replicaset 2617936164 3338832170 There’s a few different ways to do this , but i guess we will cover this later on. Thank you.

Different

Too Long; Didn't Read

In your car, at home, or at work — Bosch technology shapes many areas of life.

Kubernetes 101 #4 Rollouts

Too Long; Didn't Read

Companies Mentioned

Short Tech Stories

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

Kubernetes 101 #4 Rollouts

Too Long; Didn't Read

Companies Mentioned

Short Tech Stories

About Author

TOPICS

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES