The simply complex task of implementing Kubernetes ingress: Lessons learned
Getting traffic into a Kubernetes cluster should be simple, but its not. The range of options can be confusing, and implementing effective configuration is equally challenging. Richard Li discusses the evolution of ingress on Kubernetes, explains why ingress controllers arent necessarily the best approach, and shares a series of lessons learned about managing traffic ingress.
|Talk Title||The simply complex task of implementing Kubernetes ingress: Lessons learned|
|Speakers||Richard Li (Datawire)|
|Conf Tag||Build resilient systems at scale|
|Location||New York, New York|
|Date||September 20-22, 2016|
Getting traffic into a Kubernetes cluster should be simple, but it’s not. Richard Li explains how software architectures have evolved to take advantage of Kubernetes and discusses the implications that these changes have on ingress. Richard then covers some of the nuances of modern ingress, including authentication, resilience, and observability at the edge, explores how Kubernetes handles ingress today, with NodePorts, LoadBalancers, and ingress controllers, and shares his experience and lessons learned from using several real-world implementations of ingress on Kubernetes.