From f6cb5ebbb5c59bb4ae3cc858c4b51c2d1f4f254c Mon Sep 17 00:00:00 2001 From: Zhonghu Xu Date: Fri, 10 Mar 2023 15:57:54 +0800 Subject: [PATCH] Explicitly document workload and services can not have overlapping address in single network --- content/en/docs/ops/deployment/deployment-models/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/docs/ops/deployment/deployment-models/index.md b/content/en/docs/ops/deployment/deployment-models/index.md index 405e9f0386..8e1b0afa9a 100644 --- a/content/en/docs/ops/deployment/deployment-models/index.md +++ b/content/en/docs/ops/deployment/deployment-models/index.md @@ -197,7 +197,8 @@ fits your existing network topology. In the simplest case, a service mesh operates over a single fully connected network. In a single network model, all {{< gloss "workload instance" >}}workload instances{{< /gloss >}} -can reach each other directly without an Istio gateway. +can reach each other directly without an Istio gateway. In addition, for single network across multi-clusters, +Istio requires services and endpoints cannot have overlapping IP addresses. A single network allows Istio to configure service consumers in a uniform way across the mesh with the ability to directly address workload instances.