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

Followup fixes from #5215 (#5632) 

* Followup fixes from #5215

* remove extra bracket
This commit is contained in:
Frank Budinsky 2019-11-12 10:17:02 -05:00 committed by Istio Automation
parent 08a92bb255
commit 49de5021b8
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
content/en/blog/2019/app-identity-and-access-adapter/index.md
View File

@ -20,9 +20,9 @@ With the [App Identity and Access Adapter](https://github.com/ibm-cloud-security
transparently layers onto distributed applications and seamlessly integrates
with Kubernetes. To reduce the complexity of deployments Istio provides
behavioral insights and operational control over the service mesh as a whole.
[See Istio Architecture for more details.](/docs/ops/architecture/)
See the [Istio Architecture](/docs/ops/architecture/) for more details.
Istio uses [Envoy proxy sidecars](/blog/2019/data-plane-setup/) to mediate inbound and outbound traffic for all pods in the service mesh. Istio extracts telemetry from the Envoy sidecars and sends it to [Mixer](/docs/ops/architecture/#mixer), the Istio component responsible for collecting telemetry and policy enforcement.
Istio uses [Envoy proxy sidecars](/blog/2019/data-plane-setup/) to mediate inbound and outbound traffic for all pods in the service mesh. Istio extracts telemetry from the Envoy sidecars and sends it to [Mixer](/docs/ops/architecture/#mixer), the Istio component responsible for collecting telemetry and enforcing policy.
The App Identity and Access adapter extends the Mixer functionality by analyzing the telemetry (attributes) against various access control policies across the service mesh. The access control policies can be linked to a particular Kubernetes services and can be finely tuned to specific service endpoints. For more information about policies and telemetry, see the Istio documentation.

4
content/en/docs/concepts/traffic-management/index.md
View File

@ -528,8 +528,8 @@ traffic for services running outside of the mesh, including the following tasks:
consumed from the web, or traffic to services in legacy infrastructure.
- Define [retry](#retries), [timeout](#timeouts), and
[fault injection](#fault-injection) policies for external destinations.
- Add a service running in a Virtual Machine (VM) to the mesh by
[adding VMs your mesh](/docs/examples/virtual-machines/single-network/#running-services-on-the-added-vm).
- Run a mesh service in a Virtual Machine (VM) by
[adding VMs to your mesh](/docs/examples/virtual-machines/).
- Logically add services from a different cluster to the mesh to configure a
[multicluster Istio mesh](/docs/setup/install/multicluster/gateways/#configure-the-example-services)
on Kubernetes.

2
content/en/docs/examples/virtual-machines/bookinfo/index.md
View File

@ -37,7 +37,7 @@ https://docs.google.com/drawings/d/1G1592HlOVgtbsIqxJnmMzvy6ejIdhajCosxF1LbvspI/
- Deploy the [Bookinfo](/docs/examples/bookinfo/) sample application (in the `bookinfo` namespace).
- Create a VM named 'vm-1' in the same project as Istio cluster, and [Join the Mesh](/docs/examples/virtual-machines/single-network/).
- Create a VM named 'vm-1' in the same project as the Istio cluster, and [join the mesh](/docs/examples/virtual-machines/single-network/).
## Running MySQL on the VM