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.

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: clarify port conflict rules #4887

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
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
14 changes: 10 additions & 4 deletions keps/sig-multicluster/1645-multi-cluster-services-api/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -994,10 +994,16 @@ The conflict will be resolved by assigning precedence based on each
A derived service will be accessible with the clusterset IP at the ports
dictated by child services. If the external properties of service ports for a
set of exported services don’t match, the clusterset service will expose the
union of service ports declared on its constituent services. Should a port name
be used for multiple non-identical (`port`, `protocol`, `appProtocol`) service
ports by different constituent services, the conflict resolution policy will
determine which values are used by the derived service.
union of service ports declared on its constituent services.

Like regular services, the resulting ports must respect two rules:
- Have no duplicated names (including unnamed/empty name)
- Two ports must not have the same protocol and port number

As a result, MCS-API implementations should merge ports from constituent
services first based on port name then by the protocol and port number pair.
The conflict resolution policy will determine which of the duplicated ports
are used by the ServiceImport.

#### Headlessness

Expand Down