-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
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
KEP 1645: slightly relax the managed by requirements on EndpointSlices #4930
base: master
Are you sure you want to change the base?
KEP 1645: slightly relax the managed by requirements on EndpointSlices #4930
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MrFreezeex The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
d737f35
to
81085a4
Compare
81085a4
to
3babc13
Compare
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
3babc13
to
f21b174
Compare
/lgtm |
keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Outdated
Show resolved
Hide resolved
Relax a bit the sentence about EndpointSlice marked as not managed by the endpointslice controller as some EndpointSlice might be actually managed by the endpointslice controller directly. For instance Cilium implementation currently uses the default endpointslice controller to manage the EndpointSlice from the local cluster. The sentence below still implies that imported EndpointSlice must be managed by a MCS-API controller which means that this mixed scenario can be conformant while still keeping a strong guideline for EndpointSlice managed by a MCS-API controller. Signed-off-by: Arthur Outhenin-Chalandre <[email protected]>
f21b174
to
f341e9d
Compare
/lgtm @JeremyOT WDYT? |
/lgtm |
For instance Cilium implementation currently uses the default endpointslice controller to manage the EndpointSlice from the local cluster.
The sentence below still implies that imported EndpointSlice must be managed by a MCS-API controller which means that this mixed scenario can be conformant while still keeping a strong guideline for EndpointSlice managed by a MCS-API controller.