upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-02-03 20:40:45 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions 11

secret/pki: add known issue for slow startup times (#21083)

Browse source 
* secret/pki: add known issue for slow startup times

* fix versions

* Fix typo in link

* Clarify impact
This commit is contained in:
Jason O'Donnell 2023-06-08 15:38:21 -04:00 committed by GitHub
parent f147bc1fb1
commit 698c39f988
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 28 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
website/content/docs/upgrading/upgrade-to-1.12.x.mdx
View file

@ -199,3 +199,17 @@ vault write auth/ldap/config max_page_size=-1
#### Impacted Versions
Affects Vault 1.12.6.
### Slow Startup Time When Storing PKI Certificates
There was a regression introduced in 1.12.0 where Vault is slow to start because the
PKI secret engine performs a list operation on the stored certificates. If a large number
of certificates are stored this can cause long start times on active and standby nodes.
There is currently no workaround for this other than limiting the number of certificates stored
in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store`
flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
#### Impacted Versions
Affects Vault 1.12.0+

14
website/content/docs/upgrading/upgrade-to-1.13.x.mdx
View file

@ -141,3 +141,17 @@ Affects Vault 1.13.0 to 1.13.2. Fixed in 1.13.3.
On upgrade, all local revocations will be synchronized between
clusters; revocation requests are not persisted when failing to
write cross-cluster.
### Slow Startup Time When Storing PKI Certificates
There was a regression introduced in 1.13.0 where Vault is slow to start because the
PKI secret engine performs a list operation on the stored certificates. If a large number
of certificates are stored this can cause long start times on active and standby nodes.
There is currently no workaround for this other than limiting the number of certificates stored
in Vault via the [PKI tidy](/vault/api-docs/secret/pki.mdx#tidy) or using `no_store`
flag for [PKI roles](/vault/api-docs/secret/pki.mdx#createupdate-role).
#### Impacted Versions
Affects Vault 1.13.0+