# Upgrading the cluster using Elastic Operator

**URL:** <https://discuss.elastic.co/t/upgrading-the-cluster-using-elastic-operator/279067>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [July 19, 2021, 1:20pm UTC](https://discuss.elastic.co/t/upgrading-the-cluster-using-elastic-operator/279067 "2021-07-19T13:20:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![yubarseg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yubarseg/32/91826_2.png) [@yubarseg](https://discuss.elastic.co/u/yubarseg)\
**Post date:** [July 19, 2021, 1:20pm UTC](https://discuss.elastic.co/t/upgrading-the-cluster-using-elastic-operator/279067/1 "2021-07-19T13:20:19Z")

</div>

Hello,

I am testing different upgrade options of Elasticsearch using Elastic Operator on Kubernetes following this documentation [Upgrading the cluster](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-orchestration.html#k8s-upgrading). Example described there works fine:

- Replace dedicated master and dedicated data nodes with nodes having both master and data roles: Replace the two existing NodeSets by a single one with a different name and the appropriate Elasticsearch configuration settings.

But I was wondering if the reverse use case is also supported (split combined master/data configuration to dedicated master and data nodes).

I tried to test it out, but I get the following error:

`ReconciliationError elasticsearch/test Failed to apply spec change: adjust resources: Get "http://test-es-http.test-ns.svc:9200/_nodes/_all/no-metrics": dial tcp 10.0.67.253:9200: connect: connection refused`

Any idea if this use case is supported or not?

---

<div class="post-metadata">

**Author:** ![yubarseg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yubarseg/32/91826_2.png) [@yubarseg](https://discuss.elastic.co/u/yubarseg)\
**Post date:** [July 22, 2021, 7:06am UTC](https://discuss.elastic.co/t/upgrading-the-cluster-using-elastic-operator/279067/2 "2021-07-22T07:06:18Z")

</div>

I found the problem in my code. This case is supported as well, so this topic can be closed.

---

<div class="post-metadata">

**Author:** ![Thibault\_Richard](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/thibault_richard/32/50513_2.png) [@Thibault\_Richard](https://discuss.elastic.co/u/Thibault_Richard)\
**Post date:** [August 3, 2021, 9:02am UTC](https://discuss.elastic.co/t/upgrading-the-cluster-using-elastic-operator/279067/3 "2021-08-03T09:02:20Z")

</div>