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

Fix typos in blog (#5179) 

* Fix typos in blog

* one more
This commit is contained in:
Frank Budinsky 2019-10-17 17:30:54 -04:00 committed by Istio Automation
parent c18122c369
commit ab1da9dec2
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/blog/2019/monitoring-external-service-traffic/index.md
View File

@ -15,7 +15,7 @@ security vulnerability if an application is attempting to communicate with a
service that it should not be allowed to. Similarly, if you currently have a
policy of allowing any external service access, it is beneficial to monitor
the traffic so you can incrementally add explicit Istio configuration to allow
access and better security your cluster. In either case, having visibility into this
access and better secure your cluster. In either case, having visibility into this
traffic via telemetry is quite helpful as it enables you to create alerts and
dashboards, and better reason about your security posture. This was a highly
requested feature by production users of Istio and we are excited that the

4
content/en/blog/2019/multicluster-version-routing/index.md
View File

@ -19,7 +19,7 @@ Fortunately, Istio provides several ways to configure a service mesh so that app
can, more-or-less transparently, be part of a mesh where the services are running
in more than one cluster, i.e., in a
[multicluster deployment](/docs/concepts/deployment-models/#multiple-clusters).
The simplest way to setup a multicluster mesh, because it has no special networking requirements,
The simplest way to set up a multicluster mesh, because it has no special networking requirements,
is using a replicated
[control plane model](/docs/concepts/deployment-models/#control-plane-models).
In this configuration, each Kubernetes cluster contributing to the mesh has its own control plane,
@ -32,7 +32,7 @@ We'll show how to configure Istio route rules to call remote services in a multi
by deploying the [Bookinfo sample]({{<github_tree>}}/samples/bookinfo) with version `v1` of the `reviews` service
running in one cluster, versions `v2` and `v3` running in a second cluster.
## Setup clusters
## Set up clusters
To start, you'll need two Kubernetes clusters, both running a slightly customized configuration of Istio.