title: Kubernetes deployment not doing rolling update
body: <p>I have the following deployment in kubernetes:</p>
  
  <pre><code> apiVersion: extensions/v1beta1
   kind: Deployment
   metadata:
     labels:
       run: hello-node
     name: hello-node
     namespace: default
   spec:
     replicas: 2
     selector:
       matchLabels:
         run: hello-node
     strategy:
       rollingUpdate:
         maxSurge: 2
         maxUnavailable: 0
       type: RollingUpdate
     template:
       metadata:
         creationTimestamp: null
         labels:
           run: hello-node
       spec:
         containers:
         - image: &lt;image&gt;:&lt;tag&gt;
           imagePullPolicy: Always
           name: hello-node
           livenessProbe:
             httpGet:
               path: /rest/hello
               port: 8081
             initialDelaySeconds: 15
             timeoutSeconds: 1
           ports:
           - containerPort: 8081
             protocol: TCP
           resources:
             requests:
               cpu: 400m
           terminationMessagePath: /dev/termination-log
         dnsPolicy: ClusterFirst
         restartPolicy: Always
         securityContext: {}
         terminationGracePeriodSeconds: 30
  </code></pre>
  
  <p>The issue is that when I update my deployment to let's say a new version of my image, <code>Kubernetes</code> will instantly kill both pods with the old image, and bring two new pods with the new image. While the new pods are booting up I experience an interruption of service.</p>
  
  <p>Because of the <code>rollingUpdate</code> and the <code>livenessProbe</code> I'm expecting <code>Kubernetes</code> to do the following:</p>
  
  <ol>
  <li>Start one pod with the new image</li>
  <li>Wait for the new pod to be healthy based on the <code>livenessProbe</code></li>
  <li>Kill one pod with the old image</li>
  <li>Repeat until all pods have been migrated</li>
  </ol>
  
  <p>I am missing something here?</p>