# Want to upgrade ELK cluster from 5.6.x to 7.x w/o Kibana downtime **URL:** \ **Category:** Kibana\ **Created:** [October 3, 2019, 9:31pm UTC](https://discuss.elastic.co/t/want-to-upgrade-elk-cluster-from-5-6-x-to-7-x-w-o-kibana-downtime/202246 "2019-10-03T21:31:36Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![eherot](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eherot/32/17983_2.png) [@eherot](https://discuss.elastic.co/u/eherot)\ **Post date:** [October 3, 2019, 9:31pm UTC](https://discuss.elastic.co/t/want-to-upgrade-elk-cluster-from-5-6-x-to-7-x-w-o-kibana-downtime/202246/1 "2019-10-03T21:31:37Z")
I'm working with a 12 node cluster, so upgrading every node is likely to take a while. Currently when there is a version mismatch between any two nodes in the cluster, Kibana refuses to load. Is there any way to work around this problem so that Kibana can be online while I do this upgrade? ---
**Author:** ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)\ **Post date:** [October 11, 2019, 2:01pm UTC](https://discuss.elastic.co/t/want-to-upgrade-elk-cluster-from-5-6-x-to-7-x-w-o-kibana-downtime/202246/2 "2019-10-11T14:01:43Z")
You could set the upgraded nodes to a separate cluster and when they all finish upgrading you can point kibana to that cluster. But do keep in mind you settings for data replication and so on. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 8, 2019, 2:01pm UTC](https://discuss.elastic.co/t/want-to-upgrade-elk-cluster-from-5-6-x-to-7-x-w-o-kibana-downtime/202246/3 "2019-11-08T14:01:44Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.