# Upgrading existing helm charts **URL:** \ **Category:** Community Support\ **Tags:** helm\ **Created:** [September 15, 2020, 11:57am UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627 "2020-09-15T11:57:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Sandeep\_Paul](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/sandeep_paul/32/145_2.png) [@Sandeep\_Paul](https://community.temporal.io/u/Sandeep_Paul)\ **Post date:** [September 15, 2020, 11:57am UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/1 "2020-09-15T11:57:07Z")
Hi, For enabling rolling upgrade of the temporal helm charts. Is it in plan to add a file with delta changes to existing version of .29v of default and visibility DB. regards Sandeep ---
**Author:** ![markmark](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/markmark/32/88_2.png) [@markmark](https://community.temporal.io/u/markmark)\ **Post date:** [September 15, 2020, 5:42pm UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/3 "2020-09-15T17:42:47Z")
Hi Sandeep, thank you for this question. Our expectation is that Temporal will provide db schema migration tooling for each release that includes schema changes. It might not look like a file with delta changes, but if you have specific requirements / preferences for how the schema delta is packaged for your use case, please let us know! Thank you, Mark. ---
**Author:** ![Sandeep\_Paul](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/sandeep_paul/32/145_2.png) [@Sandeep\_Paul](https://community.temporal.io/u/Sandeep_Paul)\ **Post date:** [September 16, 2020, 4:30am UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/4 "2020-09-16T04:30:22Z")
> [@markmark](#): > > ill provide db schema migration tooling for each release that includes schema changes. It might not look like a file with delta changes, but if you have specific requirements / preferences for how the schema delta is packaged for your use case, please let us know! > > Thank you, > Mark. Hi Mark, (context: helm .29 with own mysql) Thanks for the information. Our overall intention is, 1: while upgrading from version A - B, how can we upgrade the helm chart without having to uninstall A 2: the current blocker in achieving point 1 are the two processes (DB creation,Tables creation), which we are doing as a prerequisite kubernetes Job before installing the other templates. 3: while installing B, we believe there would some addition of CREATE tables statements, which if added as a delta file for version B, we can modify the helm installation to pick version B changes while doing helm upgrade. regards Sandeep ---
**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\ **Post date:** [September 16, 2020, 6:00pm UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/5 "2020-09-16T18:00:11Z")
@markmark so if i have temporal 0.28.0 installed in my k8s, and if i just do helm upgrade things will seamlessly upgrade to 0.29.0 right? inspite of the fact that i could be using a managed sql/cassendar/es. ---
**Author:** ![markmark](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/markmark/32/88_2.png) [@markmark](https://community.temporal.io/u/markmark)\ **Post date:** [September 16, 2020, 7:01pm UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/6 "2020-09-16T19:01:49Z")
> [@madhu](#): > > so if i have temporal 0.28.0 installed in my k8s, and if i just do helm upgrade things will seamlessly upgrade to 0.29.0 right? Hi Madhu, (EDIT: Updated) Starting with any release after 0.29.0, you should be able to upgrade to a later release and preserve the data. The process _may_ involve running schema migration tools in addition to upgrading the version of images you are running (e. g. via `helm upgrade ...`). Thank you, Mark. ---
**Author:** ![madhu](https://avatars.discourse-cdn.com/v4/letter/m/a8b319/32.png) [@madhu](https://community.temporal.io/u/madhu)\ **Post date:** [September 17, 2020, 7:19am UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/7 "2020-09-17T07:19:03Z")
Thanks mark, [https://github.com/temporalio/temporal/pull/697](https://github.com/temporalio/temporal/pull/697) is a prerequisite for rolling upgrades right? ---
**Author:** ![Sandeep\_Paul](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/sandeep_paul/32/145_2.png) [@Sandeep\_Paul](https://community.temporal.io/u/Sandeep_Paul)\ **Post date:** [September 22, 2020, 10:57am UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/8 "2020-09-22T10:57:10Z")
> [@markmark](#): > > Starting with any release after 0.29.0, you should be able to upgrade to a later release and preserve the data. The process _may_ involve running schema migration tools in addition to upgrading the version of images you are running (e. g. via `helm upgrade ...` ). Hi Mark, can you please clarify “running schema migration tools”. regards Sandeep ---
**Author:** ![markmark](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/markmark/32/88_2.png) [@markmark](https://community.temporal.io/u/markmark)\ **Post date:** [September 23, 2020, 10:10pm UTC](https://community.temporal.io/t/upgrading-existing-helm-charts/627/9 "2020-09-23T22:10:54Z")
Hi Sandeep, The short answer is that the details of this are TBD. ; ) The slightly longer answer is that we currently have a tool that we use for creating keyspaces / tables and updating schemas (`temporal-cassandra-tool` and `temporal-sql-tool`), and they will likely be at the core of how schemas get upgraded. The exact user experience / steps are to be defined, and we will compose / test / document them whenever we have a release that includes a schema upgrade. Thank you, Mark.