title: Does helm upgrade on a configmap automatically inject new data into running pod?
body: <p>When issuing a helm upgrade on a running pod, my configmap is updated, but will the pod know about the configmap updated values automatically or is there another step that I need to take to inject new configmap values into the pod?</p>
  
  <p>My overall goal is to avoid having to interact with the running pod such as a delete or restart / reinstall.</p>
  
  <p>I've seen a lot of info about changing sha1sum and doing some workarounds, but my question is more basic - do pods automatically become aware of new configmap items?</p>
  
  <p>---- UPDATE --- so what we ended up doing was:</p>
  
  <p>helm upgrade -n release -f release/values.yaml <strong>--recreate-pods</strong>  </p>
  
  <p>although this terminates the existing pod, another one is instantly started upon issuing the command, meaning "near zero" downtime.</p>