Ingress, with Tim Hockin
The history of Borg influences the history of Kubernetes in many ways: Google has different teams handle “get traffic to a cluster” and “serve traffic”, so Kubernetes has a conceptual split here too. Tim Hockin, Kubernetes co-founder, Google principal engineer and former Borg/Omega team leader, joins Adam and Craig to explain the history and future of the Ingress API, why it’s taken so long to get to v1, and how it might evolve in the future.
Do you have something cool to share? Some questions? Let us know:
- web: kubernetespodcast.com
- mail: kubernetespodcast@google.com
- twitter: @kubernetespod
Chatter of the week
- Intelligence Squared: Can an AI change your mind?
- Robot or Not: Is your AI a robot?
News of the Week
- Arm joins the CNCF
- Cilium 1.4 is released
- Lightboard: week
- New EKS regions
- Kubernetes Day India schedule announced
- The Information on Kubernetes (subscription or e-mail address required)
Links from the interview
- Hello, my name is Tim Hockin, and I pronounce “kubectl” as “kubectl”
- lmctfy, Google’s open source container tool
- Kubernetes network concepts: Service and Ingress
- Annotations
- NGINX ingress
- Google Cloud BackendConfig
- Heptio Contour
- IngressRoute
- Istio v1alpha3 API
- KEP to move Ingress to v1 (GA)
- T-shirt logos
- Tim’s favourites: Brushstrokes and Pixels
- Craig’s favourite is the paint splash
- Tim Hockin on Twitter