a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
55 lines
2.1 KiB
Markdown
55 lines
2.1 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "Upgrading to Vault 0.8.0 - Guides"
|
|
sidebar_title: "Upgrade to 0.8.0"
|
|
sidebar_current: "docs-upgrading-to-0.8.0"
|
|
description: |-
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.8.0. Please read it carefully.
|
|
---
|
|
|
|
# Overview
|
|
|
|
This page contains the list of deprecations and important or breaking changes
|
|
for Vault 0.8.0 compared to the most recent release. Please read it carefully.
|
|
|
|
## Enterprise Upgrade Procedure
|
|
|
|
If you are upgrading from Vault Enterprise, you should take one of the
|
|
following upgrade paths. Please note that reindexing stops the ability of the
|
|
node to process requests while the indexing is happening. As a result, you may
|
|
want to plan the upgrade for a time when either no writes to the primary are
|
|
expected and secondaries can handle traffic (if using replication), or when
|
|
there is a maintenance window.
|
|
|
|
There are two reindex processes that need to happen during the upgrade, for two
|
|
different indexes. One will happen automatically when the cluster is upgraded
|
|
to 0.8.0. _This happens even if you are not currently using replication._ The
|
|
other can be done in one of a few ways, as follows.
|
|
|
|
### If Not Using Replication
|
|
|
|
If not using replication, no further action needs to be taken.
|
|
|
|
### If Using Replication
|
|
|
|
#### Option 1: Reindex the Primary, then Upgrade Secondaries
|
|
|
|
The first option is to issue a write to [`sys/replication/reindex`][reindex] on the
|
|
primary (it is not necessary on the secondaries). When the reindex on the
|
|
primary is finished, upgrade the secondaries, then upgrade the primary.
|
|
|
|
#### Option 2: Upgrade All Nodes Simultaneously
|
|
|
|
The second option is to upgrade all nodes to 0.8.0 at the same time. This
|
|
removes the need to perform an explicit reindex but may equate to more down
|
|
time since secondaries will not be able to service requests while the primary
|
|
is performing an explicit reindex.
|
|
|
|
## `sys/revoke-force` Requires `sudo` Capability
|
|
|
|
This path was meant to require `sudo` capability but was not implemented this
|
|
way. It now requires `sudo` capability to run.
|
|
|
|
[reindex]: https://www.vaultproject.io/api/system/replication.html#reindex-replication
|