kelseyhightower/istio-ingress-tutorial — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2018-07-26
Set up a front door for external traffic into a Kubernetes cluster using Istio's ingress component alone.
Gradually shift traffic from an old service version to a new one using Istio route rules.
Learn Istio's traffic routing pieces without committing to the full platform.
Manage load-balanced entry points for a Kubernetes-hosted application.
| kelseyhightower/istio-ingress-tutorial | codecrafters-io/build-your-own-redis | kelseyhightower/nomad-on-kubernetes | |
|---|---|---|---|
| Stars | 321 | 327 | 354 |
| Language | Shell | Shell | Shell |
| Last pushed | 2018-07-26 | — | 2018-06-26 |
| Maintenance | Dormant | — | Dormant |
| Setup difficulty | hard | moderate | hard |
| Complexity | 4/5 | 1/5 | 4/5 |
| Audience | ops devops | developer | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires provisioning dedicated servers and a load balancer for the Envoy proxy layer on top of an existing Kubernetes cluster.
The Istio Ingress Tutorial is a step-by-step guide that shows you how to route incoming web traffic into applications running on a Kubernetes cluster using a tool called Istio. Instead of forcing you to adopt an entire complex platform all at once, it walks you through setting up just the piece that handles how outside visitors reach your services. At a high level, Kubernetes is a system for running applications across many servers. When you want external users to reach those applications, you need an "ingress controller" to act as a front door. This tutorial sets up that front door using Envoy, a powerful proxy. A central component called the Istio Pilot manages these Envoy proxies and lets you set rules for how traffic flows. The architecture spreads these proxies across dedicated servers, with a load balancer sitting in front to distribute visitor traffic evenly. This guide is built for teams already using Kubernetes who want more control over their traffic routing without committing to a massive platform overhaul. For example, if you run an online store and want to gradually shift traffic from an old version of your checkout service to a new one, the route rules covered here let you do exactly that. It is aimed at infrastructure operators or engineers who need to manage how requests enter a cluster. The project is notable because it emphasizes that adopting large platforms does not have to be an all-or-nothing decision. By focusing exclusively on the ingress component, it keeps the setup lightweight while still providing robust traffic management. The tutorial breaks the process into clear steps, starting from installing client tools and provisioning infrastructure, all the way to configuring specific route rules. It also includes a clean-up script to remove all resources once you are done.
A step-by-step tutorial for setting up Istio's ingress layer alone, using Envoy proxies to route external traffic into a Kubernetes cluster without adopting all of Istio.
Mainly Shell. The stack also includes Kubernetes, Istio, Envoy.
Dormant — no commits in 2+ years (last push 2018-07-26).
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.