Aflevering 113: Goodbye Ingress-NGINX Hello Gateway API!
Aflevering 113: Goodbye Ingress-NGINX Hello Gateway API!
James, who is also a maintainer of Ingress-NGINX, explains why the project is being phased out and how the community is building its successor
Samenvatting
In this episode we sit down with James Strong, Solutions Architect at Isovalent (the team behind Cilium), to talk about one of the biggest evolutions in Kubernetes networking: the shift from Ingress-NGINX to the Gateway API.
James, who is also a maintainer of Ingress-NGINX, explains why the project is being phased out and how the community is building its successor in-gate, a new implementation designed around the Gateway API. We dive into:
- Why the Gateway API is the next-generation replacement for Ingress.
- The challenges of migrating existing workloads and dealing with technical debt.
- How the new API improves security, RBAC separation, and flexibility.
- The importance of community contribution, not just through code, but by joining discussions, testing, and providing feedback.
We also discuss common misconceptions, unusual use cases (like people trying to load balance VPNs and SFTP!), and what the future looks like for networking projects in the CNCF ecosystem.
An honest, behind-the-scenes look at the future of Kubernetes networking from someone helping to build it.
