istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

remove "single control plane" from the Shared control plane configurations

This commit is contained in:
Vadim Eisenberg 2019-07-25 19:44:16 +03:00
parent 97f9d59a12
commit 11e1caf1fa
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/docs/concepts/multicluster-deployments/index.md
View File

@ -84,8 +84,8 @@ To configure this type of multicluster topology, visit our
### Shared control plane topology
This multicluster configuration uses a single Istio control plane running on one of the clusters.
The control plane's Pilot manages services on the local and remote clusters and configures the
This multicluster configuration uses one or several Istio control planes running on some of the clusters.
The control planes' Pilots manage services on the local and remote clusters and configure the
Envoy sidecars for all of the clusters.
#### Single-network shared control plane
@ -99,9 +99,9 @@ same IP address.
caption="Istio mesh spanning multiple Kubernetes clusters with direct network access to remote pods over VPN"
>}}
In this topology, the Istio control plane is deployed on one of the clusters while all other
clusters run a simpler remote Istio configuration which connects them to the single Istio control plane
that manages all of the Envoy's as a single mesh. The IP addresses on the various clusters must not
In this topology, the Istio control plane is deployed on some of the clusters while all other
clusters run a simpler remote Istio configuration which connects them to the remote Istio control planes
that manage all of the Envoy's as a single mesh. The IP addresses on the various clusters must not
overlap and DNS resolution for services on remote clusters is not automatic. Users need to replicate
the services on every participating cluster.