From b4e815140d6781b9791713de0a96434c5f14eb13 Mon Sep 17 00:00:00 2001 From: Yoko Hyakuna Date: Tue, 2 Aug 2022 19:05:17 -0700 Subject: [PATCH] Move the IS Autopilot note from 1.11 upgrade guide (#16541) * Move the IS Autopilot note from 1.11 upgrade guide * Minor update to the verbiage * Update website/content/docs/upgrading/index.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Update website/content/docs/upgrading/index.mdx Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> * Remove extra spaces Co-authored-by: Loann Le <84412881+taoism4504@users.noreply.github.com> --- website/content/docs/upgrading/index.mdx | 15 +++++++++++---- .../content/docs/upgrading/upgrade-to-1.11.x.mdx | 10 ---------- 2 files changed, 11 insertions(+), 14 deletions(-) diff --git a/website/content/docs/upgrading/index.mdx b/website/content/docs/upgrading/index.mdx index 9a490834003e..f65c7e4dedce 100644 --- a/website/content/docs/upgrading/index.mdx +++ b/website/content/docs/upgrading/index.mdx @@ -12,7 +12,7 @@ These are general upgrade instructions for Vault for both non-HA and HA setups. _Please ensure that you also read any version-specific upgrade notes which can be found in the sidebar._ -!> **IMPORTANT NOTE:** Always back up your data before upgrading! Vault does not +!> **Important:** Always back up your data before upgrading! Vault does not make backward-compatibility guarantees for its data store. Simply replacing the newly-installed Vault binary with the previous version will not cleanly downgrade Vault, as upgrades may perform changes to the underlying data @@ -25,10 +25,17 @@ supported. The upgrade notes for each intervening version must be reviewed. The upgrade notes may describe additional steps or configuration to update before, during, or after the upgrade. -## Tutorial +### Integrated Storage Autopilot -Refer to the [Vault Upgrade Standard Procedure](https://learn.hashicorp.com/tutorials/vault/sop-upgrade) -tutorial to learn how to upgrade Vault Enterprise. +Vault 1.11 introduced [automated +upgrades](/docs/concepts/integrated-storage/autopilot#automated-upgrades) as +part of the Integrated Storage Autopilot feature. If your Vault environment is +configured to use Integrated Storage, consider leveraging this new feature to +upgrade your Vault environment. + +-> **Tutorial:** Refer to the [Automate Upgrades with Vault + Enterprise](https://learn.hashicorp.com/tutorials/vault/raft-upgrade-automation) + tutorial for more details. ## Agent diff --git a/website/content/docs/upgrading/upgrade-to-1.11.x.mdx b/website/content/docs/upgrading/upgrade-to-1.11.x.mdx index e0785746f64f..8642738d37cc 100644 --- a/website/content/docs/upgrading/upgrade-to-1.11.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.11.x.mdx @@ -18,13 +18,3 @@ path instead of `/_xpack/security` when managing Elasticsearch. If users are on an Elasticsearch version prior to 6, they will need to switch back to the old API path by setting the [bool config option](/api-docs/secret/databases/elasticdb#use_old_xpack) `use_old_xpack=true`. - -## Integrated Storage Autopilot - -Vault 1.11 introduced [automated -upgrades](/docs/concepts/integrated-storage/autopilot#automated-upgrades) as -part of the Integrated Storage Autopilot feature. If your Vault environment is -configured to use Integrated Storage, consider leveraging this new feature. See -the [Automate Upgrades with Vault -Enterprise](https://learn.hashicorp.com/tutorials/vault/raft-upgrade-automation) -tutorial for more details. \ No newline at end of file