From 5507e9d798f4d9e899d6fff685ff50ab8b92cbe7 Mon Sep 17 00:00:00 2001 From: hc-github-team-consul-core Date: Wed, 29 Nov 2023 15:16:59 -0600 Subject: [PATCH] Backport of Docs: FIPS - add cluster peering info into release/1.16.x (#19778) * backport of commit 854ccee4d4f50852980468e6617dc7fc40ad3208 * backport of commit 812cf288bdb115fbfa2a8f84e7347d76e86a0c4c * backport of commit af8aef88a50a09ef4462a7d7745162d29ecc26d3 * backport of commit 5111c406ecd0e12309bfc775c504258f085843ae --------- Co-authored-by: Jeff-Apple <79924108+Jeff-Apple@users.noreply.github.com> --- website/content/docs/enterprise/fips.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/website/content/docs/enterprise/fips.mdx b/website/content/docs/enterprise/fips.mdx index 5f5cf2819..0aca1ad20 100644 --- a/website/content/docs/enterprise/fips.mdx +++ b/website/content/docs/enterprise/fips.mdx @@ -32,6 +32,10 @@ The FIPS 140-2 variant of Consul uses separate binaries that are available from The above naming conventions, which append `.fips1402` to binary names and tags, and `-fips` to registry names, also apply to `consul-k8s`, `consul-k8s-control-plane`, `consul-dataplane`, and `consul-ecs`, which are packaged separately from Consul Enterprise. +### Cluster peering support + +A Consul cluster running FIPS variants of Consul can peer with any combination of standard (non-FIPS) Consul clusters and FIPS Consul clusters. Consul supports all cluster peering features between FIPS clusters and non-FIPS clusters. + ### Usage restrictions When using Consul Enterprise with FIPS 140-2, be aware of the following operation restrictions: