Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

KEP 1645: slightly relax the managed by requirements on EndpointSlices #4930

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+4 −3
Open

KEP 1645: slightly relax the managed by requirements on EndpointSlices #4930

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions keps/sig-multicluster/1645-multi-cluster-services-api/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -880,9 +880,10 @@ When a `ServiceExport` is created, this will cause `EndpointSlice` objects for
the underlying `Service` to be created in each importing cluster within the
clusterset, associated with the derived `ServiceImport`. One or more
`EndpointSlice` resources will exist for the exported `Service`, with each
`EndpointSlice` containing only endpoints from a single source cluster. These
`EndpointSlice` objects will be marked as managed by the clusterset service
controller, so that the endpoint slice controller doesn’t delete them.
`EndpointSlice` containing only endpoints from a single source cluster. An
`EndpointSlice` created by an mcs-controller must be marked as managed by the
mcs-controller, not the default `EndpointSlice` controller to avoid any conflicts
between the controllers.

When a service is un-exported, the associated EndpointSlices will be deleted.
The specific mechanism by which they are deleted is an implementation detail.
Expand Down