Add notes on the PKI cert generation forwarding regression#13815
Add notes on the PKI cert generation forwarding regression#13815
Conversation
| @@ -0,0 +1,10 @@ | |||
| ## PKI Certificate Generation Forwarding Regression | |||
|
|
|||
| A bug introduced in Vault 1.8 causes certificates issue by the PKI secrets engine made on a performance | |||
There was a problem hiding this comment.
| A bug introduced in Vault 1.8 causes certificates issue by the PKI secrets engine made on a performance | |
| A bug introduced in Vault 1.8 causes certificates generation requests via the PKI secrets engine made on a performance |
There was a problem hiding this comment.
I think "causes certificate generation requests via" (get rid of the pluralization of "certificates")?
| ## PKI Certificate Generation Forwarding Regression | ||
|
|
||
| A bug introduced in Vault 1.8 causes certificates issue by the PKI secrets engine made on a performance | ||
| secondary node to be forwarded to a Vault cluster's primary node. This affects horizontal scalability, but |
There was a problem hiding this comment.
I don't expect the horizontal scalability is the real issue most users, it's more about the certs/CRLs being in the wrong place. If we do want to retain this bit, I might expand it a little - not everyone's going to follow what we mean by horizontal scalability.
There was a problem hiding this comment.
Okay, I'll just drop that part.
|
@sgmiller I changed the label to "backport/website" which will open and automerge a PR to stable website and open a PR against release/1.9 for versioned docs - could you please make sure to merge the release/1.9 PR? Those don't automerge. |
|
Revision 2 |
mladlow
left a comment
There was a problem hiding this comment.
By my read this resolves @ncabatoff's comments but I don't necessarily want to speak for him. Anyway, I didn't understand this issue before reading this note and I now understand it much better, so from my perspective this is good.
No description provided.