Skip to content

Commit 2cbba6f

Browse files
authored
update mean for Endpoint API
1 parent ae7b7c0 commit 2cbba6f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

content/en/blog/_posts/2020-09-02-scaling-kubernetes-networking-endpointslices.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,4 +43,4 @@ Topology aware routing will update kube-proxy to prefer routing requests within
4343
## What does this mean for the Endpoints API?
4444
Although the EndpointSlice API is providing a newer and more scalable alternative to the Endpoints API, the Endpoints API will continue to be considered generally available and stable. The most significant change planned for the Endpoints API will involve beginning to truncate Endpoints that would otherwise run into scalability issues.
4545

46-
The Endpoints API is not going away, but many new features will rely on the EndpointSlice API. To take advantage of the new scalability and functionality that EndpointSlices provide, applications that currently consume Endpoints will likely want to consider switching to EndpointSlices in the future.
46+
The Endpoints API is not going away, but many new features will rely on the EndpointSlice API. To take advantage of the new scalability and functionality that EndpointSlices provide, applications that currently consume Endpoints will likely want to consider supporting EndpointSlices in the future.

0 commit comments

Comments
 (0)