This tutorial demonstrates how to run the Istio Ingress Controller in a Kubernetes Cluster.
[I watched Kelsey Hightower present this tutorial, which seemed like a good reason to try it myself.]
The Istio project hosts multiple components including: Pilot, Mixer, and Istio Auth. When combined these components provide a complete platform to connect, manage, and secure microservices. However, adopting Istio is not an all or nothing proposition. You can adopt only the parts you need. In this tutorial the Istio Pilot, which is responsible for the lifecycle of Envoy instances, and the Istio Ingress, a Kubernetes Ingress Controller based on Envoy, will be used to provide a robust Ingress solution.
[Ingress controllers are really interesting plus Istio offers some very interesting possibilities also.]
- Istio Pilot managed by a Deployment
- Istio Ingress Controller managed by a DaemonSet
- Runs on each node in a dedicated Istio Ingress node pool
- Frontend Load Balancer distributes traffic across multiple Istio Ingress Controllers
- Prerequisites
- Install Client Tools
- Provision the Kubernetes Infrastructure
- Provision the Istio Pilot
- Provision the Istio Ingress Controller
- Using Istio Route Rules
Run the clean-up bash script to remove all compute resources created by this tutorial:
bash clean-up
- Convert deprecated ThirdPartyResource to a CustomResourceDefinition