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

fix(architecture): remove mixer mentions from architecture doc (#6731) 

* fix(architecture): remove mixer mentions from architecture doc

Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>

* remove outdated link

Signed-off-by: Douglas Reid <douglas-reid@users.noreply.github.com>
This commit is contained in:
Istio Automation 2020-03-04 16:04:48 -08:00 committed by GitHub
parent 9dec4fbcae
commit de2d59be65
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 7 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -22,7 +22,7 @@ with Kubernetes. To reduce the complexity of deployments Istio provides
behavioral insights and operational control over the service mesh as a whole.
See the [Istio Architecture](/docs/ops/deployment/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/deployment/architecture/#mixer), the Istio component responsible for collecting telemetry and enforcing policy.
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, 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.

28
content/en/docs/ops/deployment/architecture/index.md
View File

@ -12,13 +12,10 @@ plane**.
* The **data plane** is composed of a set of intelligent proxies
([Envoy](https://www.envoyproxy.io/)) deployed as sidecars. These proxies
mediate and control all network communication between microservices along
with [Mixer](/docs/reference/config/policy-and-telemetry/), a general-purpose
policy and telemetry hub.
mediate and control all network communication between microservices. They
also collect and report telemetry on all mesh traffic.
* The **control plane** manages and configures the proxies to route traffic.
Additionally, the control plane configures Mixers to enforce policies and
collect telemetry.
The following diagram shows the different components that make up each plane:
@ -63,9 +60,8 @@ for example:
This sidecar deployment allows Istio to extract a wealth of signals about traffic behavior as
[attributes](/docs/reference/config/policy-and-telemetry/mixer-overview/#attributes).
Istio can, in turn, use these attributes in [Mixer](/docs/reference/config/policy-and-telemetry/)
to enforce policy decisions, and send them to monitoring systems to provide
information about the behavior of the entire mesh.
Istio can use these attributes to enforce policy decisions, and send them to monitoring systems
to provide information about the behavior of the entire mesh.
The sidecar proxy model also allows you to add Istio capabilities to an
existing deployment with no need to rearchitect or rewrite code. You can read
@ -83,20 +79,8 @@ Some of the Istio features and tasks enabled by Envoy proxies include:
* Security and authentication features: enforce security policies and enforce
access control and rate limiting defined through the configuration API.
### Mixer
[Mixer](/docs/reference/config/policy-and-telemetry/) is a platform-independent
component. Mixer enforces access control and usage policies across the service
mesh, and collects telemetry data from the Envoy proxy and other services. The
proxy extracts request level
[attributes](/docs/reference/config/policy-and-telemetry/mixer-overview/#attributes), and sends them
to Mixer for evaluation. You can find more information on this attribute
extraction and policy evaluation in our [Mixer Configuration
documentation](/docs/reference/config/policy-and-telemetry/mixer-overview/#configuration-model).
Mixer includes a flexible plugin model. This model enables Istio to interface
with a variety of host environments and infrastructure backends. Thus, Istio
abstracts the Envoy proxy and Istio-managed services from these details.
* Pluggable extensions model based on WebAssembly that allows for custom policy
enforcement and telemetry generation for mesh traffic.
### Pilot