Skip to content

Commit 46de654

Browse files
authored
Merge pull request #39 from Stevenjin8/patch-1
Use EndpointSlice instead of EndPointSlice
2 parents dbca0ce + 7d54e85 commit 46de654

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

site-src/api-types/service-export.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,5 @@ If multiple clusters export a Service with the same namespaced name, they will b
1010
## DNS
1111
When a ServiceExport is created, this will cause a domain name for the multi-cluster service to become accessible from within the ClusterSet. The domain name will be `<service-export-name>.<service-export-namespace>.svc.clusterset.local`.
1212

13-
## EndPointSlice
14-
When a ServiceExport is created, this will cause EndpointSlice objects for the underlying Service to be created in each cluster within the ClusterSet. One or more EndpointSlice resources will exist for each cluster that exported the Service, with each EndpointSlice containing only endpoints from its source cluster. These EndpointSlice objects are marked as managed by the ClusterSet service controller, so that the endpoint slice controller doesn’t delete them.
13+
## EndpointSlice
14+
When a ServiceExport is created, this will cause EndpointSlice objects for the underlying Service to be created in each cluster within the ClusterSet. One or more EndpointSlice resources will exist for each cluster that exported the Service, with each EndpointSlice containing only endpoints from its source cluster. These EndpointSlice objects are marked as managed by the ClusterSet service controller, so that the endpoint slice controller doesn’t delete them.

0 commit comments

Comments
 (0)