kubernetes rollout triggered on scaling

0 votes

I have a simple kubernetes deployment with 3 replicas of an nginx container.

However when I scale my deployment, it does trigger a rollout. What am I missing here?:

C:\Kubernetes>kubectl scale deployment myapp-deployment --replicas=20
deployment "myapp-deployment" scaled
C:\Kubernetes>kubectl rollout status deployment/myapp-deployment
Waiting for rollout to finish: 3 of 20 updated replicas are available...
Waiting for rollout to finish: 4 of 20 updated replicas are available...
Waiting for rollout to finish: 5 of 20 updated replicas are available...
Waiting for rollout to finish: 6 of 20 updated replicas are available...
Waiting for rollout to finish: 7 of 20 updated replicas are available...
Waiting for rollout to finish: 8 of 20 updated replicas are available...
Waiting for rollout to finish: 9 of 20 updated replicas are available...
Waiting for rollout to finish: 10 of 20 updated replicas are available...
Waiting for rollout to finish: 11 of 20 updated replicas are available...
Waiting for rollout to finish: 12 of 20 updated replicas are available...
Waiting for rollout to finish: 13 of 20 updated replicas are available...
Waiting for rollout to finish: 14 of 20 updated replicas are available...
Waiting for rollout to finish: 15 of 20 updated replicas are available...
Waiting for rollout to finish: 16 of 20 updated replicas are available...
Waiting for rollout to finish: 17 of 20 updated replicas are available...
Waiting for rollout to finish: 18 of 20 updated replicas are available...
Waiting for rollout to finish: 19 of 20 updated replicas are available...
deployment "myapp-deployment" successfully rolled out

What does this rollout mean?

Sep 4, 2018 in Kubernetes by Hannah
• 14,080 points

edited Sep 4, 2018 by Hannah 14 views

1 answer to this question.

Your answer

Your name to display (optional):
Privacy: Your email address will only be used for sending these notifications.
0 votes

when you update the pod template, the existing pods are brought down and new pods are brought up. When you just change the replica number, the existing pods are left in place and identical ones to the existing are spun up. So it's like adding to the previous rollout, not creating a new one.

answered Sep 4, 2018 by Kalgi
• 35,800 points

Related Questions In Kubernetes

0 votes
1 answer

automating cluster setup and app deplument on kubernetes

Go through Google Cloud Deployment Manager. it automates ...READ MORE

answered Jul 5, 2018 in Kubernetes by ajs3033
• 7,040 points
26 views
0 votes
1 answer

How can I access a service installed on Kubernetes from anywhere?

I have followed the link which you have ...READ MORE

answered Jul 23, 2018 in Kubernetes by Atul
• 10,200 points
73 views
0 votes
1 answer

Unable to run Kubernetes on rancher cluster

switch Docker to 1.12.x; Kubernetes doesn't support ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 35,800 points
81 views
0 votes
2 answers

keep container running on Kubernetes

Try using this CMD in your Dockerfile: CMD exec /bin/bash ...READ MORE

answered Aug 30, 2018 in Kubernetes by Nilesh
• 6,900 points
631 views
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
491 views
+3 votes
1 answer
0 votes
1 answer

Running Kubernetes on Mac

This error occurs becaouse you have to ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 35,800 points
23 views
0 votes
1 answer

“403 Insufficient Permission” while creating a Kubernetes Cluster on Google Cloud instance

To run ./cluster/kube-up.sh, you most likely need compute scope ...READ MORE

answered Aug 28, 2018 in Kubernetes by Kalgi
• 35,800 points
80 views

© 2018 Brain4ce Education Solutions Pvt. Ltd. All rights Reserved.
"PMP®","PMI®", "PMI-ACP®" and "PMBOK®" are registered marks of the Project Management Institute, Inc. MongoDB®, Mongo and the leaf logo are the registered trademarks of MongoDB, Inc.