# Elasticsearch and Kibana upgrade to v8.12.0 from v8.0.0
**URL:** https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170
**Category:** Elasticsearch
**Tags:** elastic-stack-monitoring, elastic-stack-security, docker
**Created:** [February 13, 2024, 1:00pm UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170 "2024-02-13T13:00:39Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Gaurav\_kr](https://discuss.elastic.co/u/Gaurav_kr)
#### Post date: [February 13, 2024, 1:00pm UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170/1 "2024-02-13T13:00:39Z")
Hi Team,
We are planning to upgrade elasticsearch and Kibana to v8.12.0 from v8.0.0
For beats and ELK communication wea re using ssl true and we are using API key in yaml file of beats like metricbeat.
Wanted to know if i upgrade elasticsearch and Kibana to new v8.12.0 from old v8.0.0 will it delete the API key as this will impact all beats real time data and we have to recreate the api key and replace in beats yaml files too.
Need expertise so that we do not get downtime on monitoring.
---
### Author:  [@cperzrt10](https://discuss.elastic.co/u/cperzrt10)
#### Post date: [February 13, 2024, 4:16pm UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170/2 "2024-02-13T16:16:44Z")
Hi!
No it doesnt delete the api keys.
When you update a cluster you must update first the data nodes and after all are up you restore your master nodes starting for the not ruler master.
```auto
###################Updating version########################
###step 1
PUT _cluster/settings
{
"persistent": {
"cluster.routing.allocation.enable": "primaries"
}
}
### step 2
POST _flush
## this comand in kibana console show the last master node you must restore it apears with a "*" see the image below
GET _cat/nodes
##step 3 stop the service
##step 4 update the service
##step 5 start the service
## step 6
PUT _cluster/settings
{
"persistent": {
"cluster.routing.allocation.enable": null
}
}
##step 7 every time you restart a data node and execute step 6 do NOT start the esteps until this (step 7) show in the response "100% green" ==> "... culster_name green .....100.0%"
GET _cat/health
## To restore de Master node (with no data role) only use the steps 3, 4 and 5
## remenber that restart the last master that when execute "GET _cat/nodes" you see a "*" like the image below
################### END ########################
```
Use this guide to update your cluster : [Update elasticsearch](https://www.elastic.co/guide/en/elastic-stack/8.0/upgrading-elasticsearch.html)
---
### Author:  [@Gaurav\_kr](https://discuss.elastic.co/u/Gaurav_kr)
#### Post date: [February 14, 2024, 3:58pm UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170/3 "2024-02-14T15:58:06Z")
Thanks @cperzrt10 so we will simply use new version image in docker-compose file for elastic and kibana.
**Also will it impact the current dashboards ?** if yes will export all the dashboard and once upgarde is done will import it back.
---
### Author:  [@cperzrt10](https://discuss.elastic.co/u/cperzrt10)
#### Post date: [February 15, 2024, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170/4 "2024-02-15T08:18:45Z")
Hi.
To make sure you must do a snapshot of all data. I'm not sure that if you export the dashboards, update and import that it works by the changes of the versions.
[Upgrade Kibana](https://www.elastic.co/guide/en/kibana/current/upgrade.html)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 14, 2024, 8:18am UTC](https://discuss.elastic.co/t/elasticsearch-and-kibana-upgrade-to-v8-12-0-from-v8-0-0/353170/5 "2024-03-14T08:18:54Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.