google-cloud-platform - gcp中的itsio和ESP有什么区别？

Question

两者似乎做同样的事情。根据我收集到的信息，Istio 在 Inngress 级别进行路由，在容器级别进行 ESP。我还在了解 Istio。

Answer 1

根据谷歌云documentation :

Extensible Service Proxy

The Extensible Service Proxy (ESP) is an Nginx-based high-performance, scalable proxy that runs in front of an OpenAPI or gRPC API backend and provides API management features such as authentication, monitoring, and logging. See About Endpoints and Endpoints: Architectural overview for more information.

Extensible Service Proxy V2 Beta

The Extensible Service Proxy V2 Beta (ESPv2 Beta) is an Envoy-based high-performance, scalable proxy that runs in front of an OpenAPI API backend and provides API management features such as authentication, monitoring, and logging. See About Endpoints and Endpoints: Architectural overview for more information.

ESPv2 Beta supports version 2 of the OpenAPI Specification. ESPv2 Beta does not currently support gRPC.

ESPv2 Beta is only supported for use for the Beta versions of Endpoints for Cloud Functions and for Cloud Run. ESPv2 Beta is not supported for Endpoints for App Engine, GKE, Compute Engine, or Kubernetes.

根据 istio github documentation :

Introduction

Istio is an open platform for providing a uniform way to integrate microservices, manage traffic flow across microservices, enforce policies and aggregate telemetry data. Istio's control plane provides an abstraction layer over the underlying cluster management platform, such as Kubernetes.

Istio is composed of these components:

• Envoy - Sidecar proxies per microservice to handle ingress/egress traffic between services in the cluster and from a service to external services. The proxies form a secure microservice mesh providing a rich set of functions like discovery, rich layer-7 routing, circuit breakers, policy enforcement and telemetry recording/reporting functions.

  Note: The service mesh is not an overlay network. It simplifies and enhances how microservices in an application talk to each other over the network provided by the underlying platform.

• Mixer - 代理和微服务利用中央组件来执行授权、速率限制、配额、身份验证、请求跟踪和遥测收集等策略。

• Pilot - 负责在运行时配置代理的组件。

• Citadel - 负责证书颁发和轮换的集中式组件。

• Citadel 代理 - 负责证书颁发和轮换的每个节点组件。

• Galley- 在 Istio 中验证、摄取、聚合、转换和分发配置的中央组件。

• Operator- 该组件提供用户友好的选项来操作 Istio 服务网格。

Istio 目前支持 Kubernetes 和基于 Consul 的环境。我们计划在不久的将来支持其他平台，例如 Cloud Foundry 和 Mesos。

ESP v2 Beta 也像 Istio 一样基于 Envoy 代理。然而，Istio 具有 ESP v2 尚不具备的高级功能，因为它仍处于测试阶段。至于 ESP v1，它更像是 nginx ingress。所有这些工具都能够执行路由任务，但是每个工具都有不同的底层机制，并提供不同程度的配置灵 active 和复杂性。

希望对您有所帮助。