Traffic Director: Traffic management for open service mesh

Re:Traffic Director: Traffic management for open service mesh by outside1234 on Wednesday April 10, 2019 @11:38PM (#19630959)

Is this controlling Istio under the hood?

[ Parent | on HN ]

Re:Traffic Director: Traffic management for open service mesh by puzzle on Wednesday April 10, 2019 @11:52PM (#19631023)

Kind of. It's only the traffic management part, i.e. the external load balancer. It seems to be a mix of a managed Istio Pilot plus a bunch of stuff from GCLB: anycast, backend subsetting (Envoy does not do the health checking), etc. TD just tells each client which servers to talk to. It doesn't forward traffic. And it doesn't seem to be responsible for injecting the sidecars in clients.

[ Parent | on HN ]

Re:Traffic Director: Traffic management for open service mesh by igmor on Wednesday April 10, 2019 @11:55PM (#19631036)

From documentation:

Traffic Director delivers a GCP-managed Pilot along with additional capabilities such as global load balancing and centralized health checking. However, note that Traffic Director cannot be configured using Istio APIs in this Beta release; you can use GCP APIs for configuration. Both Traffic Director and Pilot use open standard APIs (xDS v2) to communicate with service proxies.

[ Parent | on HN ]