Рет қаралды 1,468
How do you optimize the Istio ingress gateway? When and why would you need to perform this? In this video, I discuss scenarios where a single Istio ingress gateway may not be suitable for your Kubernetes environment because of the degraded performance from bearing the load of many service proxy configurations. You may be running multiple unrelated workloads (in a multi-tenant environment) with varying configurations and requirements. In situations like this, it may be better to have multiple ingress gateways that serve the different types of applications in your Kubernetes cluster. In addition to that, to avoid stressing a single ingress gateway with all the configurations for every proxy in the Istio service mesh, you can optimize each gateway's performance by filtering the proxies it should know about.
#kubernetes #istio
Timestamps:
00:00 - Introduction
00:20 - Running multiple gateways for different purposes
00:55 - Improving ingress gateway performance by creating multiple gateways
01:59 - Improving ingress gateway performance by filtering the virtual services attached to it
02:18 - The cost implication of running multiple gateways in a cloud environment
02:35 - Code-walk-through and demo
Other resources:
Using Istio Gateway to Route Traffic to Microservices on Amazon EKS - • Using Istio Gateway to...
Secure Istio Gateway Traffic with TLS Encryption on Amazon EKS - • Secure Istio Gateway T...
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!