open-vault/website/content/docs/upgrading/upgrade-to-1.14.x.mdx
hc-github-team-secure-vault-core 2eff100d5d
Backport of Remove duplicate partial reference from release-notes into release/1.14.x (#24087)
* Remove duplicate partial reference from release-notes (#24081)

* remove partial references from release-notes that link to upgrade guides, and change link in partial to anchor

* Clarify leak is memory consumption

There is no leak of information.

* update references in table

* update table to include range for affected versions

---------

Co-authored-by: Meggie Ladlow <meggie@hashicorp.com>

* update link in known issues table

---------

Co-authored-by: davidadeleon <56207066+davidadeleon@users.noreply.github.com>
Co-authored-by: Meggie Ladlow <meggie@hashicorp.com>
2023-11-09 15:42:53 -05:00

63 lines
2.1 KiB
Plaintext

---
layout: docs
page_title: Upgrade to Vault 1.14.x
description: |-
Deprecations, important or breaking changes, and remediation recommendations
for anyone upgrading to 1.14.x from Vault 1.13.x.
---
# Upgrade to Vault 1.14.x
The Vault 1.14.x upgrade guide contains information on deprecations, important
or breaking changes, and remediation recommendations for anyone upgrading from
Vault 1.13. **Please read carefully**.
## Feature deprecations and EOL
### Duplicative Docker images
As of Vault 1.14 we will no longer update the the `vault` Docker image.
Only the [Verified Publisher](https://hub.docker.com/r/hashicorp/vault)
`hashicorp/vault` image will be updated on DockerHub.
Users of [Official Images](https://hub.docker.com/_/vault) need to use
`docker pull hashicorp/vault:<version>` instead of `docker pull vault:<version>`
to get newer versions of Vault in Docker images. Currently, HashiCorp publishes
and updates identical Docker images of Vault as Verified Publisher and
Official images separately.
## Important changes
`vault.raft_storage.bolt.write.time` has been corrected from a summary to a counter to more accurately reflect that it
is measuring cumulative time writing, and not the distribution of individual write times.
### Application of Sentinel Role Governing Policies (RGPs) via identity groups
@include 'application-of-sentinel-rgps-via-identity-groups.mdx'
## Known issues and workarounds
@include 'known-issues/ui-pki-control-groups.mdx'
@include 'known-issues/update-primary-data-loss.mdx'
@include 'known-issues/update-primary-addrs-panic.mdx'
@include 'known-issues/ui-safari-login-screen.mdx'
@include 'known-issues/aws-static-roles.mdx'
@include 'known-issues/transit-managed-keys-panics.mdx'
@include 'known-issues/transit-managed-keys-sign-fails.mdx'
@include 'known-issues/ui-collapsed-navbar.mdx'
@include 'known-issues/internal-error-namespace-missing-policy.mdx'
@include 'known-issues/ephemeral-loggers-memory-leak.mdx'
@include 'known-issues/sublogger-levels-unchanged-on-reload.mdx'
@include 'known-issues/expiration-metrics-fatal-error.mdx'