Istio中的Mixer和Pilot之间的区别? [英] Difference between Mixer and Pilot in Istio?
问题描述
我已经阅读了文档，但似乎无法理解它们之间的差异.有重叠吗?我的意思是，我想在他们之间划定界限，以了解他们的责任，并避免他们与网格中的特使进行沟通. (如果可能，还带有示例用例)
I have read the docs, but seem not able to understand differences between them. Is there any overlap? I mean I would like to draw a definite boundary between them to understand their responsibilities and w.r.t their communication with the envoy proxies in the mesh. (with examples use-cases if possible)
推荐答案
Istio服务网格提供以下功能:
The Istio Service Mesh provides the following functionalities:
- 路由.例如，有90％的流量流向的版本1 微服务，其余的10％用于版本2. 具体请求转到版本1，所有其他请求转到 版本2，视情况而定.并且:a)重写b) 重定向
- 支持微服务开发，部署和测试:a)超时b)重试c)断路器d)负载平衡e)故障注入以进行测试
- 报告:记录，分布式跟踪，遥测
- 政策执行
- 确保微服务与强身份之间的安全通信.
- Routing. For example 90% of the traffic goes to the version 1 of a microservice and the remaining 10% goes to the version 2. Or some specific requests go to the version 1 and all the others to the version 2, according to some condition. And also: a) rewrite b) redirect
- Support for microservices development, deployment and testing: a) timeouts b) retries c) circuit breakers d) load balancing e) fault injection for testing
- Reporting: Logging, Distributed Tracing, Telemetry
- Policy enforcement
- Secure communication between micro services and strong identity.
飞行员负责项目1和2.混合器负责项目3和4.城堡(以前为CA，之前为Auth)负责项目5.
Pilot is responsible for the items 1 and 2. Mixer is responsible for the items 3 and 4. Citadel (previously CA, previously Auth) is responsible for the item 5.
Sidecar代理Envoy从Pilot获取其路由和配置表，以实施项目1和2.Envoy向Mixer报告有关每个请求的信息，以实施项目3.Envoy要求Mixer允许或禁止请求以实施项目4.特使从城堡获得证书以实施项目5.
Envoy, the sidecar proxy, gets its routing and configuration tables from Pilot to implement the items 1 and 2. Envoy reports to Mixer about each request, to implement the item 3. Envoy asks Mixer to allow or forbid requests, to implement the item 4. Envoy gets certificates from Citadel to implement the item 5.
这篇关于Istio中的Mixer和Pilot之间的区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
