One of the glaring challenges of deploying microservices to Kubernetes is figuring out optimal and secure network communication from outside the cluster to your services inside of it and network communication between the services themselves. In some scenarios, we can use Kubernetes services like LoadBalancers and NodePorts to expose our applications to the world. However, there are use cases where this isn't the best approach. A better and safer practice is establishing a single point of entry into your cluster that can also manage HTTP traffic and smart routing. I'll discuss how a tool like Istio can help with accomplishing this. Istio is an open-source implementation of a service mesh and is an agnostic middleware solution that handles network communication for your applications. You can use Istio gateways and virtual services to open a doorway to the microservices in your cluster and securely route that traffic to the relevant destination services.
In this video, I'll talk about how you can use the Istio ingress gateway and virtual services to establish a single entry point into your cluster, and route traffic to your microservices in an Amazon EKS cluster.
#kubernetes #istio #servicemesh
Timestamps:
00:00 - Introduction
00:42 - Using Kubernetes Services to expose microservices to external traffic
01:51 - Istio overview
02:53 - Service mesh analogy for routing in microservices
04:59 - Overview of architecture with Istio ingress gateway in Amazon EKS cluster
05:59 - Code walk-through of Istio configuration resources: Gateway and Virtual Service
09:58 - Demo of Istio gateway, virtual services, and microservices deployed to Amazon EKS cluster
Repositories with source code:
github.com/LukeMwila/istio-ga...
github.com/LukeMwila/microser...
Connect:
GitHub: github.com/LukeMwila
Twitter: / luke9ine
Medium: / outlier.developer
LinkedIn: / lukonde-mwila-25103345
If you found this video helpful, please like the video and subscribe to the channel!