luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

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>
This commit is contained in:
hc-github-team-consul-core 2023-11-29 15:16:59 -06:00 committed by GitHub
parent 0cd190f8d9
commit 5507e9d798
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/docs/enterprise/fips.mdx
View File

@ -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: