Re:AWS App Mesh – Service Mesh for Microservices on AWS
by jeremyjh on Wednesday November 28, 2018 @07:59PM
(#18557255)
GP asked about Service objects though. k8s natively provides name resolution, traffic routing and load balancing to your defined service objects. So what does Envoy do for me that k8s does not do itself?
Re:AWS App Mesh – Service Mesh for Microservices on AWS
by manigandham on Wednesday November 28, 2018 @08:39PM
(#18557408)
More protocol support, retries, rate-limits, circuit-breakers, traffic mirroring, better load-balancing, faster proxy performance, complex routing, fine-grained security policies with pluggable authentication, and in-depth monitoring with integrated tracing.
Smaller clusters or services don't need it. The docs overview page is worth a read: https://istio.io/docs/concepts/what-is-istio/
Re:AWS App Mesh – Service Mesh for Microservices on AWS
by jsmeaton on Wednesday November 28, 2018 @09:03PM
(#18557483)
Thanks! I was wondering if mesh effectively replaces services and why, and you've answered that.
Re:AWS App Mesh – Service Mesh for Microservices on AWS
by gauravphoenix on Wednesday November 28, 2018 @08:09PM
(#18557298)
things like layer 7 control, you can say - "don't allow HTTP GET on /supersecret". Also, Isito is gRPC aware
Re:AWS App Mesh – Service Mesh for Microservices on AWS
by andrewstuart2 on Wednesday November 28, 2018 @10:47PM
(#18557906)
This brings about a major problem with centralized route management, though, in that you then must build all of your access controls around URLs rather than deeper business logic.
Istio offers much more, but as far as anything but coarse-grained "this service will never need to talk to this other service" access control, I'd still much rather write the logic in the code where it has access to a lot more domain knowledge.
Re:AWS App Mesh – Service Mesh for Microservices on AWS
by gauravphoenix on Wednesday November 28, 2018 @11:58PM
(#18558213)
if you want just simple layer 4 ACLs among the services, I recommend just using NetworkPolicies[1] of k8s.
Personally, I think that Istio is overly complex but then so is k8s :)
[1] https://kubernetes.io/docs/concepts/services-networking/netw...
Istio is for east/west traffic within your K8S cluster, designed to connect your services together by moving all the network traffic through the Envoy proxy. It is usually done by wrapping your deployments with an extra sidecar pod (automatically using K8S APIs) that intercepts all the networking to other services and pods. You would still use a load balancer or ingress to route external traffic into the cluster, although there are options like Heptio Contour that also use Envoy for this.
This provides a single data and control plane to centralize all network reliability, security, service discovery, and monitoring.