How We Built Contour, and What You Can Learn From Our Experience
In 2017 Heptio launched Contour, a Kubernetes Ingress controller built using the Envoy proxy project from Lyft. This session will cover: - Why we chose Envoy as the data plane for our ingress contro …
| Talk Title | How We Built Contour, and What You Can Learn From Our Experience |
| Speakers | Dave Cheney (Staff engineer, Heptio) |
| Conference | KubeCon + CloudNativeCon Europe |
| Conf Tag | |
| Location | Copenhagen, Denmark |
| Date | Apr 30-May 4, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
In 2017 Heptio launched Contour, a Kubernetes Ingress controller built using the Envoy proxy project from Lyft. This session will cover: - Why we chose Envoy as the data plane for our ingress controller. - How Contour works as a translator from Kubernetes to Envoy objects. The parts that were a good match, the parts that weren’t, and how we dealt with it. - Traps, pitfalls, and ambiguities in the Ingress spec. - Specific patterns we developed to reliably watching many different kinds of API resources at the same time. The presentation will also give real world advice on the traps involved in the components that make up a management server, the k8s Go client, gRPC, and concurrency issues.
