Kubernetes Traffic Management using Istio

Abstract

When infrastructures transition from monolithic to microservices, containers might provide consistency and granularity in resource management. We can now treat one computer as multiple computers, thanks to microservices. This decreased resource waste by enabling programs to scale up and down computers in response to demand. But how can traffic be directed to services that are hosted on-premises, in a hybrid cloud, or on multi cloud deployments? The idea is to use service mesh to handle such scenarios in microservices. The idea of service mesh is to increase Kubernetes’ efficacy and security. One use of this service mesh concept is Istio. In this paper, we also discuss why we need Istio even though Kubernetes has Ingress.