Skip to content

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.

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

Closed
wants to merge 1 commit into from
Closed

KEP 1645: relax the ServiceExportConflict requirements #5436

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
10 changes: 6 additions & 4 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 @@ -1003,10 +1003,12 @@ services. If these properties are out of sync for a subset of exported services,
there is no clear way to determine how a service should be accessed.

Conflict resolution policy: **If any properties have conflicting values that can
not simply be merged, a `ServiceExportConflict` condition will be set on all
`ServiceExport`s for the conflicted service with a description of the conflict.
The conflict will be resolved by assigning precedence based on each
`ServiceExport`'s `creationTimestamp`, from oldest to newest.**
not simply be merged, the conflict will be resolved by assigning precedence based on each
`ServiceExport`'s `creationTimestamp`, from oldest to newest. A `ServiceExportConflict` condition
will be set on the `ServiceExport`s for the conflicted service with a description of the conflict.
It is recommended to set the `ServiceExportConflict` condition on all the constituent `ServiceExport`s
to provide maximum visibility to the user, however, if this is not feasible for an implementation,
at a minimum it should be set on the constituent `ServiceExport`s that introduced the conflict.**

#### Service Port

Expand Down