diff --git a/website/content/docs/enterprise/lts.mdx b/website/content/docs/enterprise/lts.mdx new file mode 100644 index 0000000000..2dccf2e7e8 --- /dev/null +++ b/website/content/docs/enterprise/lts.mdx @@ -0,0 +1,195 @@ +--- +layout: docs +page_title: Long-term support for Vault +description: >- + Learn the details about long-term support for Vault Enterprise. +--- + +# Long-term support for Vault + +@include 'alerts/enterprise-only.mdx' + +Long-term support (LTS) eases upgrade requirements for installations that cannot +upgrade frequently, quickly, or easily. + +## LTS summary + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
QuestionAnswer
+ Who should consider long-term support? + + Enterprise customers using Vault for sensitive or critical workflows. +
+ What is long-term support? + + Extended support for select, major Vault Enterprise versions. HashiCorp + provides one year of standard support for all Vault Enterprise versions, + which includes feature updates and critical patches. LTS extends support + one additional year with critical patches (2 years in total). +
+ Where do I enable long-term support? + + You do not need to download a separate binary or set a flag for LTS + support. As long as you select an LTS Vault Enterprise version when + you install or upgrade your + Vault instance, LTS is included. +
+ When are LTS versions released? + + As of Vault Enterprise 1.16, the first major release of a calendar year includes + long-term support. +
+ Why is there a risk to updating to a non-LTS Vault Enterprise version? + + If you upgrade to a non-LTS Vault Enterprise version, your Vault instance + is limited to standard support and will stop receiving critical updates + when that version leaves + the standard support window. +
+ How do I update my LTS Vault Enterprise installation? + + Follow your existing Vault upgrade process, but allow extra time for the + possibility of transitional upgrades across multiple Vault versions. +
+ + + +## Who should consider long-term support? + +Vault upgrades are challenging, especially for sensitive or critical workflows, +extensive integrations, and large-scale deployments. Strict upgrade policies +also require significant planning, testing, and employee hours to execute +successfully. + +Customers who need assurances that their current installation will receive +critical bug fixes and security patches with minimal service disruptions should +consider moving to a Vault Enterprise version with long-term support. + + + +## What is long-term support? + +**Standard support** for Vault Enterprise includes: + +- performance improvements. +- feature updates and improvements. +- bug fixes. +- security patches. +- CVE patches to correct vulnerabilities and exposures. + +The standard +[support period and end of life policy](https://go.hashi.co/vault-support-policy) +covers "N−2" versions, which means, at any given time, HashiCorp supports +the current version ("N") and the two previous versions ("N−2"). + +Vault versions typically update 3 times per calendar year (CY), which means that +standard support for a given Vault version lasts approximately 1 year: + +Version | Release date | Standard support ends +------- | -------------------- | ---------------------- +1.16 | CY24 Q1 (2024-03-27) | CY25 Q1 (1.19 release) +1.15 | CY23 Q3 (2023-09-27) | CY24 Q3 (1.18 release) +1.14 | CY23 Q2 (2023-06-21) | CY24 Q2 (1.17 release) +1.13 | CY23 Q1 (2023-03-01) | CY24 Q1 (2024-03-27) +1.12 | CY22 Q4 (2022-10-12) | CY23 Q3 (2023-09-27) + +**Long-term support** extends support for specific Vault Enterprise versions for +an additional year with: + +- patches for bugs that may cause outages. +- patches for critical vulnerabilities and exposures. +- high-risk security patches. + +After the first year, LTS Vault versions move from standard support to long-term +support for an additional year. + + + +## Where do I enable long-term support? + +You do not need to download a separate binary or set a flag for LTS support. As +long as you select an LTS Vault Enterprise version (e.g., 1.16, 1.19) when you +[install](/vault/install) or [upgrade](/vault/docs/upgrading) your Vault +instance, LTS is included. + + + +## When are LTS versions released? + +As of Vault Enterprise 1.16, the first release of a calendar year includes +long-term support. + +LTS versions overlap by one year with the previous LTS version entering its +long-term support window when the new LTS version begins its standard support +window. + + + +## Why is there a risk to updating to a non-LTS Vault Enterprise version? + +Long-term support is intended for Enterprise customers who cannot upgrade +frequently enough to stay within the standard support timeline of one year. The +goal is to establish a predictable upgrade path with a longer timeline rather +than extending the lifetime for every Vault version. + +Long-term support ensures your Vault Enterprise version continues to receive +critical patches for an additional year. If you upgrade to a non-LTS version, +you are moving your Vault instance to a version that lacks extended support, +which means your version stops receiving updates once it leaves the standard +support window: + +Version | Expected release | Standard support ends | Long-term support ends +------- | ---------------- | ---------------------- | --------------------- +1.19 | CY25 Q1 | CY26 Q1 (1.22 release) | CY27 Q1 (1.25 release) +1.18 | CY24 Q3 | CY25 Q3 (1.21 release) | Not provided +1.17 | CY24 Q2 | CY25 Q2 (1.20 release) | Not provided +1.16 | CY24 Q1 | CY25 Q1 (1.19 release) | CY26 Q1 (1.22 release) + +If a newer version of Vault Enterprise includes features you want to take +advantage of, you have two options: + +1. Wait for the next available LTS release to maintain long-term support. +1. Upgrade immediately, then upgrade to an LTS release before the standard + support window expires. + + + +## How do I upgrade my Vault Enterprise LTS installation? + +You should follow your existing upgrade process for major version upgrades but +allow additional time. Upgrading from version LTS to LTS+1 translates to jumping +3 major Vault Enterprise versions, which **may** require transitional upgrades +to move through the intermediate Vault versions. \ No newline at end of file diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json index 3367d7d88f..f99b2ee630 100644 --- a/website/data/docs-nav-data.json +++ b/website/data/docs-nav-data.json @@ -2680,6 +2680,10 @@ } ] }, + { + "title": "Long-term support (LTS)", + "path": "enterprise/lts" + }, { "title": "Replication", "routes": [