From f4a0f069cec3a3945cb35069875868e8181751e5 Mon Sep 17 00:00:00 2001 From: Zhiying Lin Date: Fri, 1 Aug 2025 16:28:48 +0800 Subject: [PATCH] KEP 1645: clarify the impact of conflict condition --- keps/sig-multicluster/1645-multi-cluster-services-api/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/keps/sig-multicluster/1645-multi-cluster-services-api/README.md b/keps/sig-multicluster/1645-multi-cluster-services-api/README.md index 4ce6a0ed07b..406126d3bff 100644 --- a/keps/sig-multicluster/1645-multi-cluster-services-api/README.md +++ b/keps/sig-multicluster/1645-multi-cluster-services-api/README.md @@ -991,6 +991,8 @@ not simply be merged, a `ServiceExportConflict` condition will be set on all The conflict will be resolved by assigning precedence based on each `ServiceExport`'s `creationTimestamp`, from oldest to newest.** +**Note:** When a `ServiceExport`'s conflict condition changes from `False` to `True` due to this resolution policy, runtime traffic remains unaffected. The oldest cluster will win the conflict and continue to be referenced in the `ServiceImport`, maintaining service continuity. Conversely, when the conflict condition transitions from `True` to `False` (for example, when the oldest cluster's service is unexported), the `ServiceImport` may remain unchanged to avoid potentially disruptive changes to active traffic patterns. + #### Service Port A derived service will be accessible with the clusterset IP at the ports