Skip to content

Commit eb74af5

Browse files
committed
Clarifying future of Endpoints in EndpointSlice KEP
1 parent 0dbcef0 commit eb74af5

File tree

1 file changed

+3
-4
lines changed
  • keps/sig-network/20190603-endpointslices

1 file changed

+3
-4
lines changed

keps/sig-network/20190603-endpointslices/README.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -482,10 +482,9 @@ transform EndpointSlices into that same data structure.
482482

483483
### Endpoints Controller (classic)
484484

485-
In order to ensure backwards compatibility for external consumer of the core/v1
486-
Endpoints API, the existing Endpoints controller will keep running until the
487-
API is EOL. After EndpointSlices become GA, the Endpoints controller will
488-
gradually limit functionality.
485+
The existing Endpoints controller will continue to run. After EndpointSlices
486+
become GA, the Endpoints controller may limit the number of endpoints it stores
487+
per resource.
489488

490489
* Kubernetes 1.20: If the number of endpoints in one Endpoints object exceeds
491490
1000, set `endpoints.kubernetes.io/over-capacity` label to "warning".

0 commit comments

Comments
 (0)