The most popular Ingress controller for Kubernetes is ingress-nginx, created in 2015 by Alejandro de Brito Fontes. Alejandro stepped down earlier this year, and the project is now maintained by a team including Ricardo Katz. Learn the history and what’s in the new 1.0 release from a pair of South American self-proclaimed sysadmins.

Do you have something cool to share? Some questions? Let us know:

Chatter of the week

New Zealand cinema worker left red-faced after voicemail blooper
- Uncensored version on TikTok

News of the week

Amazon EKS Anywhere is GA and EKS Connector is in preview
CNI 1.0.1
Red Kubes makes Otomi self-service features free of charge
Scale down mode and custom policy for Microsoft AKS
k8ssandra moves from Helm to operator
API server tracing in Kubernetes 1.22 by David Ashpole
- Episode 113
How Docker Broke In Half, by Scott Carey]
- Episode 156, with Sebastien Pahl
- Episode 110, with Adrian Ionel

Links from the interview

ingress-nginx
Early computing
History of Ingress
- Ingress announced in Kubernetes 1.1
- CoreOS Fleet
- Service loadbalancer
- kube-haproxy-router
- Kubernetes Ingress proposal issue
- ingress-gce
ingress-nginx:
- Alejandro’s proposal for ingress-nginx
- Original PR
- Alejandro’s bare metal cluster - then and now
- Ricardo’s early contributions
- Note that NGINX Inc. have their own Ingress controller, for the open source or commercial versions of NGINX
  - Their comparison of the two versions
Supporting open source:
- Alejandro steps down as ingress-nginx maintainer
  - He actually tried earlier, but no-one else stepped up!
- Core Infrastructure Initiative fund for supporting the Internet
- xkcd on internet dependencies
- Episode 116, with Alex Ellis
The future:
Alejandro de Brito Fontes on Twitter
Ricardo Katz on Twitter

ingress-nginx, with Alejandro de Brito Fontes and Ricardo Katz

Kubernetes Podcast from Google