Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add known issue about PKI secrets engine with Consul #18003

Merged
merged 3 commits into from
Nov 17, 2022
Merged

Add known issue about PKI secrets engine with Consul #18003

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e4b08f4
Add known issue about PKI secrets engine with Consul
yhyakuna Nov 17, 2022
7c2d365
Added KB article URL
yhyakuna Nov 17, 2022
ff5618c
Update website/content/docs/secrets/pki/index.mdx
yhyakuna Nov 17, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Added KB article URL
  • Loading branch information
@yhyakuna
yhyakuna committed Nov 17, 2022
commit 7c2d365a4e4e212a8d3d506b952b314049732e23
2 changes: 1 addition & 1 deletion website/content/docs/release-notes/1.11.0.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ You are using the Vault CA provider if either of the following configurations ex
- The Consul server agent configuration option [connect.ca_provider](/consul/docs/agent/config/config-files#connect_ca_provider) is set to “vault”, or
- The Consul on Kubernetes Helm Chart [global.secretsBackend.vault.connectCA](/consul/docs/k8s/helm#v-global-secretsbackend-vault-connectca) value is configured.

-> **NOTE:** Refer to the [Knowledge Base article]() for more information about the underlying cause and recommended workaround.
-> **NOTE:** Refer to the [Knowledge Base article](https://support.hashicorp.com/hc/en-us/articles/11308460105491) for more information about the underlying cause and recommended workaround.

## Feature Deprecations and EOL

Expand Down
9 changes: 5 additions & 4 deletions website/content/docs/secrets/pki/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,13 +8,14 @@ description: The PKI secrets engine for Vault generates TLS certificates.

@include 'x509-sha1-deprecation.mdx'

!> **Consul users:** Do not use [Vault
!> **Vault 1.11.0+ incompatible as Consul CA provider:** Do not use [Vault
v1.11.0+](/vault/docs/release-notes/1.11.0#known-issues) as Consul’s Connect CA
provider — the intermediate CA will become unable to issue the leaf nodes
required by service mesh and all actions (if using auto-encrypt or auto-config,
and using mTLS for server-to-server communication). Refer to the [Knowledge Base
article]() for more information about the underlying cause and recommended
workaround.
and using mTLS for server-to-server communication). If you are already using
Vault 1.11.0+ as a Connect CA, refer to the [Knowledge Base
article](https://support.hashicorp.com/hc/en-us/articles/11308460105491) for
more information about the underlying cause and recommended workaround.
yhyakuna marked this conversation as resolved.
Show resolved Hide resolved

The PKI secrets engine generates dynamic X.509 certificates. With this secrets
engine, services can get certificates without going through the usual manual
Expand Down