mirror of https://github.com/istio/istio.io.git
Align multi-cluster examples with new terminology (#4925)
* Align multi-cluster examples with new terminology * Update content/en/docs/setup/install/multicluster/_index.md Co-Authored-By: Rigs Caballero <grca@google.com> * Update content/en/docs/setup/install/multicluster/_index.md Co-Authored-By: Rigs Caballero <grca@google.com> * Update content/en/docs/setup/install/multicluster/gateways/index.md Co-Authored-By: Rigs Caballero <grca@google.com>
This commit is contained in:
Frank Budinsky
Istio Automation
parent
c05d6c082b
commit
4210222e60
|
|
@ -1,20 +1,20 @@
|
|||
---
|
||||
title: Multicluster Installation
|
||||
title: Multi-cluster Installation
|
||||
description: Configure an Istio mesh spanning multiple Kubernetes clusters.
|
||||
weight: 30
|
||||
aliases:
|
||||
- /docs/setup/kubernetes/multicluster-install/
|
||||
- /docs/setup/kubernetes/multicluster/
|
||||
- /docs/setup/kubernetes/install/multicluster/
|
||||
keywords: [kubernetes,multicluster]
|
||||
keywords: [kubernetes,multi-cluster]
|
||||
---
|
||||
|
||||
{{< tip >}}
|
||||
Note that these instructions are not mutually exclusive.
|
||||
In a large multicluster mesh, composed from more than two clusters,
|
||||
In a large multi-cluster deployment, composed from more than two clusters,
|
||||
a combination of the approaches can be used. For example,
|
||||
two clusters might share a control plane while a third has its own.
|
||||
{{< /tip >}}
|
||||
|
||||
Refer to the [multicluster service mesh](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
Refer to the [multi-cluster deployment model](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
concept documentation for more information.
|
||||
|
|
|
|||
|
|
@ -1,19 +1,19 @@
|
|||
---
|
||||
title: Dedicated control planes
|
||||
description: Install an Istio mesh across multiple Kubernetes clusters with individually deployed control planes.
|
||||
title: Replicated control planes
|
||||
description: Install an Istio mesh across multiple Kubernetes clusters with replicated control plane instances.
|
||||
weight: 2
|
||||
aliases:
|
||||
- /docs/setup/kubernetes/multicluster-install/gateways/
|
||||
- /docs/examples/multicluster/gateways/
|
||||
- /docs/tasks/multicluster/gateways/
|
||||
- /docs/setup/kubernetes/install/multicluster/gateways/
|
||||
keywords: [kubernetes,multicluster,gateway]
|
||||
keywords: [kubernetes,multi-cluster,gateway]
|
||||
---
|
||||
|
||||
Follow this guide to install an Istio
|
||||
[multicluster service mesh](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
with individually deployed Istio control planes in every cluster and using gateways to
|
||||
connect services across clusters.
|
||||
[multi-cluster deployment](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
with replicated [control plane](/docs/concepts/deployment-models/#control-plane-models) instances
|
||||
in every cluster and using gateways to connect services across clusters.
|
||||
|
||||
Instead of using a shared Istio control plane to manage the mesh,
|
||||
in this configuration each cluster has its own Istio control plane
|
||||
|
|
|
|||
|
|
@ -2,15 +2,15 @@
|
|||
title: Shared control plane (multi-network)
|
||||
description: Install an Istio mesh across multiple Kubernetes clusters using a shared control plane for diconnected cluster networks.
|
||||
weight: 85
|
||||
keywords: [kubernetes,multicluster]
|
||||
keywords: [kubernetes,multi-cluster]
|
||||
aliases:
|
||||
- /docs/examples/multicluster/split-horizon-eds/
|
||||
- /docs/tasks/multicluster/split-horizon-eds/
|
||||
- /docs/setup/kubernetes/install/multicluster/shared-gateways/
|
||||
---
|
||||
|
||||
Follow this guide to configure a multicluster mesh using a suitable
|
||||
[control plane model](/docs/concepts/deployment-models/#control-plane-models)
|
||||
Follow this guide to configure a multi-cluster mesh using a shared
|
||||
[control plane](/docs/concepts/deployment-models/#control-plane-models)
|
||||
with gateways to connect network-isolated clusters.
|
||||
Istio's location-aware service routing feature is used to route requests to different endpoints,
|
||||
depending on the location of the request source.
|
||||
|
|
@ -39,7 +39,7 @@ No VPN connectivity nor direct network access between workloads in different clu
|
|||
|
||||
{{< boilerplate kubectl-multicluster-contexts >}}
|
||||
|
||||
## Setup the multicluster mesh
|
||||
## Setup the multi-cluster mesh
|
||||
|
||||
In this configuration you install Istio with mutual TLS enabled for both the control plane and application pods.
|
||||
For the shared root CA, you create a `cacerts` secret on both `cluster1` and `cluster2` clusters using the same Istio
|
||||
|
|
@ -54,7 +54,7 @@ This will be used to access pilot on `cluster1` securely using the ingress gatew
|
|||
1. Use Helm to create the Istio deployment YAML for `cluster1`:
|
||||
|
||||
{{< warning >}}
|
||||
When you enable the additional components necessary for multicluster operation, the resource footprint
|
||||
When you enable the additional components necessary for multi-cluster operation, the resource footprint
|
||||
of the Istio control plane may increase beyond the capacity of the default Kubernetes cluster you created when
|
||||
completing the [Platform setup](/docs/setup/platform-setup/) steps.
|
||||
If the Istio services aren't getting scheduled due to insufficient CPU or memory, consider
|
||||
|
|
|
|||
|
|
@ -2,23 +2,23 @@
|
|||
title: Shared control plane (single-network)
|
||||
description: Install an Istio mesh across multiple Kubernetes clusters with a shared control plane and VPN connectivity between clusters.
|
||||
weight: 5
|
||||
keywords: [kubernetes,multicluster,federation,vpn]
|
||||
keywords: [kubernetes,multi-cluster,federation,vpn]
|
||||
aliases:
|
||||
- /docs/setup/kubernetes/multicluster-install/vpn/
|
||||
- /docs/setup/kubernetes/install/multicluster/vpn/
|
||||
- /docs/setup/kubernetes/install/multicluster/shared-vpn/
|
||||
---
|
||||
|
||||
Follow this guide to install an Istio [multicluster service mesh](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
Follow this guide to install an Istio [multi-cluster service mesh](/docs/concepts/deployment-models/#multiple-clusters)
|
||||
where the Kubernetes cluster services and the applications in each cluster
|
||||
have the capability to expose their internal Kubernetes network to other
|
||||
clusters.
|
||||
|
||||
In this configuration, multiple Kubernetes control planes running
|
||||
a remote configuration connect to a **single** Istio control plane.
|
||||
In this configuration, multiple Kubernetes clusters running
|
||||
a remote configuration connect to a shared Istio
|
||||
[control plane](/docs/concepts/deployment-models/#control-plane-models).
|
||||
Once one or more remote Kubernetes clusters are connected to the
|
||||
Istio control plane, Envoy can then communicate with the **single**
|
||||
control plane and form a mesh network across multiple clusters.
|
||||
Istio control plane, Envoy can then form a mesh network across multiple clusters.
|
||||
|
||||
{{< image width="80%" link="./multicluster-with-vpn.svg" caption="Istio mesh spanning multiple Kubernetes clusters with direct network access to remote pods over VPN" >}}
|
||||
|
||||
|
|
@ -33,7 +33,7 @@ control plane and form a mesh network across multiple clusters.
|
|||
meeting the following requirements:
|
||||
|
||||
* Individual cluster Pod CIDR ranges and service CIDR ranges must be unique
|
||||
across the multicluster environment and may not overlap.
|
||||
across the multi-cluster environment and may not overlap.
|
||||
|
||||
* All pod CIDRs in every cluster must be routable to each other.
|
||||
|
||||
|
|
@ -41,7 +41,7 @@ across the multicluster environment and may not overlap.
|
|||
|
||||
* Helm **2.10 or newer**. The use of Tiller is optional.
|
||||
|
||||
This guide describes how to install a multicluster Istio topology using the
|
||||
This guide describes how to install a multi-cluster Istio topology using the
|
||||
manifests and Helm charts provided within the Istio repository.
|
||||
|
||||
## Deploy the local control plane
|
||||
|
|
@ -389,7 +389,7 @@ all clusters.
|
|||
## Deployment considerations
|
||||
|
||||
The previous procedures provide a simple and step-by-step guide to deploy a
|
||||
multicluster environment. A production environment might require additional
|
||||
multi-cluster environment. A production environment might require additional
|
||||
steps or more complex deployment options. The procedures gather the endpoint
|
||||
IPs of the Istio services and use them to invoke Helm. This process creates
|
||||
Istio services on the remote clusters. As part of creating those services and
|
||||
|
|
@ -451,7 +451,7 @@ This method provides two alternatives:
|
|||
* Re-use the default Istio ingress gateway installed with the provided
|
||||
manifests or Helm charts. You only need to add the correct destination rules.
|
||||
|
||||
* Create another Istio ingress gateway specifically for the multicluster.
|
||||
* Create another Istio ingress gateway specifically for the multi-cluster.
|
||||
|
||||
## Security
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue