# Upgrade elastic in kubernetes

**URL:** <https://discuss.elastic.co/t/upgrade-elastic-in-kubernetes/193232>\
**Category:** Elasticsearch\
**Created:** [August 1, 2019, 12:22am UTC](https://discuss.elastic.co/t/upgrade-elastic-in-kubernetes/193232 "2019-08-01T00:22:07Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![soandosnc](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@soandosnc](https://discuss.elastic.co/u/soandosnc)\
**Post date:** [August 1, 2019, 12:22am UTC](https://discuss.elastic.co/t/upgrade-elastic-in-kubernetes/193232/1 "2019-08-01T00:22:07Z")

</div>

I have elastic 7.2 installed in kubernetes (via the elastic helm chart, secure example). How can I upgrade this to 7.3 (preferably in a rolling way)?

---

<div class="post-metadata">

**Author:** ![michael.russell](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.russell/32/27889_2.png) [@michael.russell](https://discuss.elastic.co/u/michael.russell)\
**Post date:** [August 1, 2019, 2:36pm UTC](https://discuss.elastic.co/t/upgrade-elastic-in-kubernetes/193232/2 "2019-08-01T14:36:00Z")

</div>

The upgrade steps are the same as any non kubernetes managed cluster. The helm chart does help you with a few of the steps though.

Make sure to read through [https://www.elastic.co/guide/en/elasticsearch/reference/7.3/setup-upgrade.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/setup-upgrade.html) and [https://www.elastic.co/guide/en/elasticsearch/reference/7.3/rolling-upgrades.html](https://www.elastic.co/guide/en/elasticsearch/reference/7.3/rolling-upgrades.html). The most important step being to test this first in a dev environment.

From the rolling upgrade guide steps 4 through to 11 will be covered by the helm chart. Instead of "4. Shut down a single node" and "5. Upgrade the node you shut down" you will instead be setting `imageTag: 7.3.0` to initiate the rolling upgrade. If you are using the default `imageTag` values you will instead just upgrade the helm chart version to 7.3.0.

The helm chart configures the statefulset with a readinessProbe that waits for the cluster health to be `green` in between node upgrades. This automates the "stop each node and upgrade them while waiting for the cluster to become healthy again" part of the upgrade guide.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 29, 2019, 2:36pm UTC](https://discuss.elastic.co/t/upgrade-elastic-in-kubernetes/193232/3 "2019-08-29T14:36:08Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.