Skip to content

Commit 5f95fec

Browse files
Kubernetes fleet - address comments
1 parent 1ef878f commit 5f95fec

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/kubernetes-fleet/architectural-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ Fleet can be used to set up layer 4 multi-cluster load balancing across workload
7676

7777
For multi-cluster load balancing, Fleet requires target clusters to be using [Azure CNI networking](../aks/configure-azure-cni.md). Azure CNI networking enables pod IPs to be directly addressable on the Azure virtual network so that they can be routed to from the Azure Load Balancer.
7878

79-
The ServiceExport itself can be propagated from the fleet cluster to a member cluster using the Kubernetes resource propagation feature describe above, or it can be created directly on the member cluster. Once this ServiceExport resource is created, it results in a ServiceImport being created on the fleet cluster and all other member clusters to build the awareness of the service
79+
The ServiceExport itself can be propagated from the fleet cluster to a member cluster using the Kubernetes resource propagation feature describe above, or it can be created directly on the member cluster. Once this ServiceExport resource is created, it results in a ServiceImport being created on the fleet cluster, and all other member clusters to build the awareness of the service
8080

8181
The user can then create a `MultiClusterService` custom resource to indicate that they want to set up Layer 4 multi-cluster load balancing. This `MultiClusterService` results in the member cluster mapped Azure Load Balancer being configured to load balance incoming traffic across endpoints of this service on multiple member clusters.
8282

0 commit comments

Comments
 (0)