Skip to content

Commit 994585b

Browse files
authored
Merge pull request #55235 from rh-tokeefe/OSSM-3242
OSSM-3242: update doc to say “2.1 or later” in federation section
2 parents cd0b180 + 448a492 commit 994585b

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

modules/ossm-federation-create-meshPeer.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This module included in the following assemblies:
1212
* Two or more {product-title} 4.6 or above clusters.
1313
* The clusters must already be networked.
1414
* The load balancers supporting the services associated with the federation gateways must be configured to support raw TLS traffic.
15-
* Each cluster must have a version 2.1 `ServiceMeshControlPlane` configured to support federation deployed.
15+
* Each cluster must have a version 2.1 or later `ServiceMeshControlPlane` configured to support federation deployed.
1616
* An account with the `cluster-admin` role.
1717
1818
////

modules/ossm-federation-prerequisites.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This module included in the following assemblies:
99
The {SMProductName} federated approach to joining meshes has the following prerequisites:
1010

1111
* Two or more {product-title} 4.6 or above clusters.
12-
* Federation was introduced in {SMProductName} 2.1. You must have the {SMProductName} 2.1 Operator installed on each mesh that you want to federate.
13-
* You must have a version 2.1 `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
12+
* Federation was introduced in {SMProductName} 2.1 or later. You must have the {SMProductName} 2.1 or later Operator installed on each mesh that you want to federate.
13+
* You must have a version 2.1 or later `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
1414
* You must configure the load balancers supporting the services associated with the federation gateways to support raw TLS traffic. Federation traffic consists of HTTPS for discovery and raw encrypted TCP for service traffic.
1515
* Services that you want to expose to another mesh should be deployed before you can export and import them. However, this is not a strict requirement. You can specify service names that do not yet exist for export/import. When you deploy the services named in the `ExportedServiceSet` and `ImportedServiceSet` they will be automatically made available for export/import.

0 commit comments

Comments
 (0)