-
Notifications
You must be signed in to change notification settings - Fork 1.5k
KEP 1645: relax the ServiceExportConflict requirements #5436
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
base: master
Are you sure you want to change the base?
Conversation
The KEP states that "a ServiceExportConflict condition will be set on all ServiceExports for the conflicted service", however this assumes an implementation has a central controller that has access to all the constituent ServiceExports or that each cluster has access to the ServiceExports on every other cluster but this may not be the case. This PR modifies the language to recommend the condition be set on all ServiceExports but not require it. See the motivation and further discussion here: kubernetes-sigs/mcs-api#111 (comment) Signed-off-by: Tom Pantelis <tompantelis@gmail.com>
/cc @MrFreezeex |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: MrFreezeex, tpantelis 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 |
/lgtm Discussed in June 25th, 2025 SIG-Multicluster meeting, see notes at https://docs.google.com/document/d/18mk62nOXE_MCSSnb4yJD_8UadtzJrYyJxFwbrgabHe8/edit?tab=t.0#heading=h.gxm49ag2wja7 Thanks for updating this - definitely makes sense that the original language would have been much easier to implement in a centralized model. |
/cc @lauralorenz |
This looks good to me too, but if I approve it it will merge immediately, I would like feedback from more participants in the discussion 😉. |
The KEP states that "a ServiceExportConflict condition will be set on all ServiceExports for the conflicted service", however this assumes an implementation has a central controller that has access to all the constituent
ServiceExports
or that each cluster has access to theServiceExports
on every other cluster but this may not be the case.This PR modifies the language to recommend the condition be set on all
ServiceExports
but not require it.See the motivation and further discussion here:
kubernetes-sigs/mcs-api#111 (comment)
Issue link: Multi-Cluster Services API #1645