<p>I'm running more than one replicas of pods with kubernetes <code>deployment</code>
and I'd like to update the replicas to use updated <code>configmap</code> in a rolling way. same like rolling-update works.</p>

<p>So that kubernetes will terminate pod and start sending traffic to the newly updated pods one at a time until all pods will be updated.</p>

<p>Can I use rolling-update with deployment?</p>

<p>Applying a change to the Deployment object will trigger a rolling-update. From the <a href="https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#updating-a-deployment" rel="noreferrer">docs</a>:</p>

<blockquote>
  <p>A Deployment’s rollout is triggered if and only if the Deployment’s pod template (that is, .spec.template) is changed, for example if the labels or container images of the template are updated. Other updates, such as scaling the Deployment, do not trigger a rollout. </p>
</blockquote>

<p>So if you want to trigger a rolling update to update your configmap I would suggest you update a metadata label. Perhaps a <code>CONFIG_VER</code> key.</p>
