whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Documenting EndpointSlice deduplication requirements

Browse Source
This commit is contained in:
Rob Scott
2020-08-11 17:35:06 -07:00
parent d9784dc5b4
commit 9bca5270fe
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/endpoint-slices.md
+9
View File
@@ -192,6 +192,15 @@ necessary soon anyway. Rolling updates of Deployments also provide a natural
repacking of EndpointSlices with all Pods and their corresponding endpoints repacking of EndpointSlices with all Pods and their corresponding endpoints
getting replaced. getting replaced.
### Duplicate endpoints
Due to the nature of EndpointSlice changes, endpoints may be represented in more
than one EndpointSlice at the same time. This naturally occurs as changes to
different EndpointSlice objects can arrive at the Kubernetes client watch/cache
at different times. Implementations using EndpointSlice must be able to have the
endpoint appear in more than one slice. A reference implementation of how to
perform endpoint deduplication can be found in the `EndpointSliceCache`
implementation in `kube-proxy`.
## {{% heading "whatsnext" %}} ## {{% heading "whatsnext" %}}