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.

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

Update wording on WAN fed and intermediate_pki_path #17850

Merged
merged 2 commits into from
Jun 27, 2023
Merged
Changes from all commits
Commits
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
6 changes: 4 additions & 2 deletions website/content/docs/connect/ca/vault.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -139,8 +139,10 @@ The key after the slash refers to the corresponding option name in the agent con
path does not exist, Consul will attempt to mount and configure this
automatically.

When WAN Federation is enabled, every secondary
datacenter must specify a unique `intermediate_pki_path`.
When WAN federation is enabled, every secondary datacenter that shares a common Vault cluster
must specify a unique `intermediate_pki_path`. If a Vault cluster is not used by more than one Consul datacenter,
then you do not need to specify a unique value for the `intermediate_pki_path`. We still recommend using a
unique `intermediate_pki_path` for each datacenter, however, to improve operational and diagnostic clarity.

- `IntermediatePKINamespace` / `intermediate_pki_namespace` (`string: <optional>`) - The absolute namespace
that the `IntermediatePKIPath` is in. Setting this parameter overrides the `Namespace` option for the `IntermediatePKIPath`. Introduced in 1.12.3.
Expand Down