# How does upgrading kibana affect the plugins on kibana

**URL:** <https://discuss.elastic.co/t/how-does-upgrading-kibana-affect-the-plugins-on-kibana/58200>\
**Category:** Kibana\
**Created:** [August 16, 2016, 11:43pm UTC](https://discuss.elastic.co/t/how-does-upgrading-kibana-affect-the-plugins-on-kibana/58200 "2016-08-16T23:43:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arpan](https://avatars.discourse-cdn.com/v4/letter/a/e480ec/32.png) [@arpan](https://discuss.elastic.co/u/arpan)\
**Post date:** [August 16, 2016, 11:43pm UTC](https://discuss.elastic.co/t/how-does-upgrading-kibana-affect-the-plugins-on-kibana/58200/1 "2016-08-16T23:43:58Z")

</div>

I was wondering whether the plugins on kibana need to be reinstalled everytime kibana is upgraded? Is this also the case with elasticsearch plugins and upgrading elasticsearch?

Is there any way around this?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 17, 2016, 3:26am UTC](https://discuss.elastic.co/t/how-does-upgrading-kibana-affect-the-plugins-on-kibana/58200/2 "2016-08-17T03:26:45Z")

</div>

Yeah you do need to do this, and yes, it is frustrating.

I thought there was an issue on GH about having some kind of `upgrade` functionality in the `plugin` command, but I cannot see one. Please do create one though! 🙂

---

<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:** [July 6, 2017, 1:41pm UTC](https://discuss.elastic.co/t/how-does-upgrading-kibana-affect-the-plugins-on-kibana/58200/3 "2017-07-06T13:41:01Z")

</div>