mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-22 23:21:08 +02:00
0660ea6fac
* Update README Let contributors know that docs will now be located in UDR * Add comments to each mdx doc Comment has been added to all mdx docs that are not partials * chore: added changelog changelog check failure * wip: removed changelog * Fix content errors * Doc spacing * Update website/content/docs/deploy/kubernetes/vso/helm.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com> --------- Co-authored-by: jonathanfrappier <92055993+jonathanfrappier@users.noreply.github.com> Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
33 lines
1.5 KiB
Plaintext
33 lines
1.5 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: LTS Vault upgrades
|
|
description: >-
|
|
General guidance for LTS upgrades
|
|
---
|
|
|
|
> [!IMPORTANT]
|
|
> **Documentation Update:** Product documentation, which were located in this repository under `/website`, are now located in [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs), colocated with all other product documentation. Contributions to this content should be done in the `web-unified-docs` repo, and not this one. Changes made to `/website` content in this repo will not be reflected on the developer.hashicorp.com website.
|
|
|
|
# Long-term support Vault upgrades
|
|
|
|
[Long-term support](/vault/docs/enterprise/) offers extended maintenance through
|
|
minor releases for select, major Vault Enterprise versions.
|
|
|
|
Current LTS release | Extended maintenance release
|
|
------------------- | ----------------------------
|
|
1.19.x | 1.16.x
|
|
|
|
Before you perform a direct LTS upgrade from an extended maintenance release to
|
|
the current LTS release, we recommend reviewing the following summary of
|
|
functional changes and known issues to determine the likely impact on your Vault
|
|
deployment.
|
|
|
|
Functional changes affect how Vault works including new requirements, new
|
|
defaults, new behavior, and breaking changes. In some cases, we recommend specific
|
|
actions before or after upgrading to mitigate the impact of a functional change.
|
|
|
|
Unresolved nown issues may have suggested workarounds or mitagation stratagies
|
|
you should consider before upgrading.
|
|
|
|
@include 'release-notes/change-summary/lts/1_16-to-1_19.mdx'
|