chapter thirteen
This chapter covers
- How to incorporate legacy workloads into Istio’s service mesh
- Explains the process to install and configure the
istio-agentin virtual machines
- Elaborates how identity is provisioned for virtual machines
- How cluster services are exposed to the VMs, and the opposite: how the services running in the VM are exposed to cluster services
- Elaborates how the DNS Proxy resolves FQDNs of cluster services
So far we’ve covered Istio service mesh from the perspective of containers and Kubernetes. In reality, however, workloads frequently run on Virtual Machines (VMs) or physical machines. Containers and Kubernetes are likely used in an effort to modernize a technology stack, and here we show how to bridge these two worlds at the application-networking layer with Istio. You might wonder, why wouldn’t we simply modernize legacy workloads and run those in a Kubernetes cluster? Instead of the alternative of integrating VMs into the mesh. We too recommend that whenever possible, but here are a few cases when it’s not—or at least not when considering the cost: