# Kubernetes RollingUpdate - how to respect readinessProbe?

**URL:** <https://discuss.kubernetes.io/t/kubernetes-rollingupdate-how-to-respect-readinessprobe/2959>\
**Category:** General Discussions\
**Created:** [October 1, 2018, 11:25am UTC](https://discuss.kubernetes.io/t/kubernetes-rollingupdate-how-to-respect-readinessprobe/2959 "2018-10-01T11:25:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbr84](https://avatars.discourse-cdn.com/v4/letter/d/b5e925/32.png) [@dbr84](https://discuss.kubernetes.io/u/dbr84)\
**Post date:** [October 1, 2018, 11:25am UTC](https://discuss.kubernetes.io/t/kubernetes-rollingupdate-how-to-respect-readinessprobe/2959/1 "2018-10-01T11:25:11Z")

</div>

We have deployments with the following strategy:

```auto
      replicas: 6
      strategy:  
          type: RollingUpdate  
          RollingUpdate:  
            maxUnavailable: 1  
            maxSurge: 100%  

```

The deployments also have readiness (and liveness) probes:

```auto
readinessProbe:  
            httpGet:  
              path: /  
              port: http  
            initialDelaySeconds: 30  

```

The issue I am seeing is that Kubernetes instantly terminates the old replicas when doing an upgrade. It does not wait for the new pods to become ready before moving on.

What am I missing here?

---

<div class="post-metadata">

**Author:** ![sander1095](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.kubernetes.io/sander1095/32/6746_2.png) [@sander1095](https://discuss.kubernetes.io/u/sander1095)\
**Post date:** [January 20, 2021, 9:14am UTC](https://discuss.kubernetes.io/t/kubernetes-rollingupdate-how-to-respect-readinessprobe/2959/2 "2021-01-20T09:14:14Z")

</div>

Hi! Did you ever figure this out? If so, what is the solution?