[Release Notes] Add a note about storage support for VE (#17597)
* Add a note about storage support * Add a row for VE storage backend
This commit is contained in:
parent
3f25394b89
commit
46cd8069be
|
@ -20,6 +20,7 @@ This announcement page is maintained and updated periodically to communicate imp
|
|||
|
||||
| Feature | Deprecation announcement | End of Support | Feature Removal | Migration Path/Impact | Resources |
|
||||
| ------------------------------------------------- | ------------------------ | -------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| Vault Enterprise storage backend | N/A | v1.12 | N/A | Use [Integrated Storage](/docs/configuration/storage/raft) or [Consul](/docs/configuration/storage/consul) as your Vault's storage backend. Vault Enterprise will no longer start up if configured to use a storage backend other than Integrated Storage or Consul. | [Upgrade Guide](/docs/upgrading/upgrade-to-1.12.x) |
|
||||
| Vault generation of Dynamic SSH Keys | v0.7.1 | N/A | v1.13 | Use the alternative [signed SSH certificates](/docs/secrets/ssh/signed-ssh-certificates) feature which supports key pair generation as of Vault 1.12. SSH certificates do not require an external connection from Vault to provision the key/certificate and more secure than having Vault provision dynamic SSH keys. | [SSH Certificates](/docs/secrets/ssh/signed-ssh-certificates) |
|
||||
| [Duplicative Docker Images](https://hub.docker.com/_/vault) | v1.12 | 1.13 | v1.14 | HashiCorp publishes identical Docker images of Vault. One set is published as a [Verified Publisher](https://hub.docker.com/r/hashicorp/vault). A second set is published as [Docker Official Images](https://hub.docker.com/_/vault). Upon feature removal, only the Verified Publisher images will be published. | [The Verified Publisher Program](https://docs.docker.com/docker-hub/publish/)
|
||||
| Etcd V2 API (OSS) | v1.9 | N/A | v1.10 | The Etcd v2 has been deprecated with the release of Etcd v3.5, and will be decomissioned by Etcd v3.6. Etcd v2 API has been removed in Vaut 1.10. Users of Etcd storage backend must migrate Vault storage to an Etcd V3 cluster prior to upgrading to Vault 1.10. All storage migrations should be backed up prior to migration. | [Etcd Storage Backend](/docs/configuration/storage/etcd) |
|
||||
|
|
|
@ -27,6 +27,8 @@ Some of these enhancements and changes in this release include the following:
|
|||
- **Redis Database Secrets Engine** is now available to manage static roles or generation of dynamic credentials, as well as root credential rotation on a stand-alone Redis server.
|
||||
- **AWS Elasticache Database Secrets Engine** is introduced to manage static credentials for AWS Elasticache instances.
|
||||
|
||||
~> **Vault Enterprise:** Use [Integrated Storage](/docs/configuration/storage/raft) or [Consul](/docs/configuration/storage/consul) as your Vault's storage backend. Vault Enterprise will no longer start up if configured to use a storage backend other than Integrated Storage or Consul. (See the [Upgrade Guide](/docs/upgrading/upgrade-to-1.12.x).)
|
||||
|
||||
## New Features
|
||||
|
||||
This section describes the new features introduced in Vault 1.12.0.
|
||||
|
|
Loading…
Reference in New Issue