Managing Microservices on Kubernetes with Istio

last week ibm and google announced istio , an open platform to connect, manage, and secure microservices. istio improves the visibility of the data flowing between the different services and the good news for developers is that you don’t have to change your code.

there is good documentation available, but in a nutshell, istio inserts proxies in pods which are called instead of the custom containers (services) directly. this allows istio to control and monitor the requests to the services. as a developer, you simply use istio to automatically add a bunch of additional containers and pods to your kubernetes deployments without having to change your app.

the istio website explains the concepts in more detail. as jason mcgee writes in this blog instio’s main functionality is:

• automatic zone-aware load balancing and failover for http/1.1, http/2, grpc, and tcp traffic.
• fine-grained control of traffic behavior with rich routing rules, fault tolerance, and fault injection.
• a pluggable policy layer and configuration api supporting access controls, rate limits and quotas.
• automatic metrics, logs and traces for all traffic within a cluster, including cluster ingress and egress.
• secure service-to-service authentication with strong identity assertions between services in a cluster.

i’ve installed the bookinfo sample to try the functionality. it was very easy to set up, both on minikube and on ibm bluemix . i like especially the dashboard (grafana) which visualizes metrics like request rates, success/failure rates, etc., in a cluster.

the servicegraph addon provides a graphical visualization of the service interaction graph for the cluster.

with the zipkin dashboard, you can see the invocation chains of microservices.

if you want to try out istio, follow these instructions and set up the sample .