1--- 2layout: docs 3page_title: Upgrading to Vault 0.8.0 - Guides 4sidebar_title: Upgrade to 0.8.0 5description: |- 6 This page contains the list of deprecations and important or breaking changes 7 for Vault 0.8.0. Please read it carefully. 8--- 9 10# Overview 11 12This page contains the list of deprecations and important or breaking changes 13for Vault 0.8.0 compared to the most recent release. Please read it carefully. 14 15## Enterprise Upgrade Procedure 16 17If you are upgrading from Vault Enterprise, you should take one of the 18following upgrade paths. Please note that reindexing stops the ability of the 19node to process requests while the indexing is happening. As a result, you may 20want to plan the upgrade for a time when either no writes to the primary are 21expected and secondaries can handle traffic (if using replication), or when 22there is a maintenance window. 23 24There are two reindex processes that need to happen during the upgrade, for two 25different indexes. One will happen automatically when the cluster is upgraded 26to 0.8.0. _This happens even if you are not currently using replication._ The 27other can be done in one of a few ways, as follows. 28 29### If Not Using Replication 30 31If not using replication, no further action needs to be taken. 32 33### If Using Replication 34 35#### Option 1: Reindex the Primary, then Upgrade Secondaries 36 37The first option is to issue a write to [`sys/replication/reindex`][reindex] on the 38primary (it is not necessary on the secondaries). When the reindex on the 39primary is finished, upgrade the secondaries, then upgrade the primary. 40 41#### Option 2: Upgrade All Nodes Simultaneously 42 43The second option is to upgrade all nodes to 0.8.0 at the same time. This 44removes the need to perform an explicit reindex but may equate to more down 45time since secondaries will not be able to service requests while the primary 46is performing an explicit reindex. 47 48## `sys/revoke-force` Requires `sudo` Capability 49 50This path was meant to require `sudo` capability but was not implemented this 51way. It now requires `sudo` capability to run. 52 53[reindex]: /api/system/replication#reindex-replication 54