mirror of https://github.com/istio/istio.io.git
Added references to glossary (#5201)
* Added reference to mixer * Added reference for Pilot * Added reference for Pilot
This commit is contained in:
parent
241bab8ab9
commit
0aefbf4a95
|
@ -2,7 +2,7 @@
|
|||
title: Adapters
|
||||
---
|
||||
|
||||
Adapters are plug-ins to Mixer, Istio's [policy and telemetry](/docs/reference/config/policy-and-telemetry/) component, which enable it to interface
|
||||
Adapters are plug-ins to [Mixer](#mixer), Istio's [policy and telemetry](/docs/reference/config/policy-and-telemetry/) component, which enable it to interface
|
||||
with an open-ended set of infrastructure backends that deliver core functionality, such as logging,
|
||||
monitoring, quotas, ACL checking, and more.
|
||||
The exact set of adapters used at runtime is determined through configuration and can easily be
|
||||
|
|
|
@ -7,7 +7,7 @@ and their corresponding [service endpoints](#service-endpoint), running in a ser
|
|||
Istio uses the service registry to generate [Envoy](#envoy) configuration.
|
||||
|
||||
Istio does not provide [service discovery](https://en.wikipedia.org/wiki/Service_discovery),
|
||||
although most services are automatically added to the registry by Pilot
|
||||
although most services are automatically added to the registry by [Pilot](#pilot)
|
||||
adapters that reflect the discovered services of the underlying platform (Kubernetes, Consul, plain DNS).
|
||||
Additional services can also be registered manually using a
|
||||
[`ServiceEntry`](/docs/concepts/traffic-management/#service-entries) configuration.
|
||||
|
|
Loading…
Reference in New Issue