You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/service-sync.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The purpose of this feature is to facilitate exposing a service in one cluster t
6
6
7
7
When you use [Cilium](https://docs.cilium.io/en/latest/overview/intro/) CNI in multiple related Kubernetes Clusters, you can use its ClusterMesh features to extend networking across them.
8
8
9
-
When using a ClusterMesh, you cant load balance Kubernetes services over the clusters, or **expose a service on one cluster as a local service on the other ones**. Is this later use case that this Keess feature targets, to make it easier for our users to configure such service exposure across clusters.
9
+
When using a ClusterMesh, you can load balance Kubernetes services over the clusters, or **expose a service on one cluster as a local service on the other ones**. Is this later use case that this Keess feature targets, to make it easier for our users to configure such service exposure across clusters.
10
10
11
11
Cilium enables that through the concept of [Global Services](https://docs.cilium.io/en/latest/network/clustermesh/services/#load-balancing-with-global-services). They are primarily made to balance across service instances deployed to many clusters. It will expose the remote endpoints inside each cluster's local service.
0 commit comments