# Upgrading from ECK 0.9.0

**URL:** <https://discuss.elastic.co/t/upgrading-from-eck-0-9-0/313580>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [September 2, 2022, 6:14pm UTC](https://discuss.elastic.co/t/upgrading-from-eck-0-9-0/313580 "2022-09-02T18:14:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![charles3](https://avatars.discourse-cdn.com/v4/letter/c/f07891/32.png) [@charles3](https://discuss.elastic.co/u/charles3)\
**Post date:** [September 2, 2022, 6:14pm UTC](https://discuss.elastic.co/t/upgrading-from-eck-0-9-0/313580/1 "2022-09-02T18:14:46Z")

</div>

Is there a guide for upgrading from ECK 0.9.0 to 1.0.0-beta1?

I've followed the [Upgrade Guide](https://www.elastic.co/guide/en/cloud-on-k8s/1.0-beta/k8s-upgrading-eck.html) and it always results in the deletion of the persistent volumes and, ultimately, the loss of data.

In the last test that I ran, the v1beta1 Elasticsearch resource couldn't be created because it used the same name as the v1alpha1 resource that was already running. I assumed that kubernetes would be able to reconcile the difference, but I think I've gotten that wrong.

The only thing I can think of now is to create a new v1beta1 Elasticsearch cluster in the same kubernetes cluster and restore a snapshot from the v1alpha1 cluster. Unfortunately, I can't create a new separate cluster.

---

<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:** [September 30, 2022, 6:14pm UTC](https://discuss.elastic.co/t/upgrading-from-eck-0-9-0/313580/2 "2022-09-30T18:14:47Z")

</div>

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