Skip to content

[enterprise-4.13] OSSM-3242: update doc to say “2.1 or later” in federation section #55273

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

Merged
merged 1 commit into from
Jan 27, 2023
Merged

[enterprise-4.13] OSSM-3242: update doc to say “2.1 or later” in federation section #55273

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion modules/ossm-federation-create-meshPeer.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ This module included in the following assemblies:
* Two or more {product-title} 4.6 or above clusters.
* The clusters must already be networked.
* The load balancers supporting the services associated with the federation gateways must be configured to support raw TLS traffic.
* Each cluster must have a version 2.1 `ServiceMeshControlPlane` configured to support federation deployed.
* Each cluster must have a version 2.1 or later `ServiceMeshControlPlane` configured to support federation deployed.
* An account with the `cluster-admin` role.

////
Expand Down
4 changes: 2 additions & 2 deletions modules/ossm-federation-prerequisites.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ This module included in the following assemblies:
The {SMProductName} federated approach to joining meshes has the following prerequisites:

* Two or more {product-title} 4.6 or above clusters.
* Federation was introduced in {SMProductName} 2.1. You must have the {SMProductName} 2.1 Operator installed on each mesh that you want to federate.
* You must have a version 2.1 `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
* 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.
* You must have a version 2.1 or later `ServiceMeshControlPlane` deployed on each mesh that you want to federate.
* 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.
* 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.