In this presentation and hands-on workshop, we will cover the difference between Kubernetes Ingress and Istio Ingress Gateway. A production end-user facing application should have an “Ingress” to expose itself to the outside world. While Kubernetes provides the “Ingress” resource for this purpose, its featureset is limited depending on the kind of Ingress Controller (usually nginx) being used.

The other option is to leverage Istio and take advantage of its more featureful Ingress Gateway resource, even if our application Pods themselves are not using sidecar proxies (pure Kubernetes). We can do so by incrementally adopting Istio’s feature: Ingress Gateway - which uses Envoy proxy as the gateway (as opposed to nginx). Let’s explore the two approaches in this presentation and see how Istio can help manage your ingress traffic.

This meetup will include a short presentation on introducing Ingress resource in Kubernetes and Istio basics. The session will provide lab environments for attendees to gain hands-on experience for exposing an application via Ingress.

Agenda:

6:00 - 6:30 Check-in & Enjoy Refreshments provided by Mirantis
6:30 - 6:35 Welcome
6:35 - 7:00 Presentation Content
7:00 - 7:45 Hands-on content w/speaker led demo
7:45 - 8:00 Q&A

Bio:

Andrew Lee started his early career in a QA position for Open Networking Lab, where he gained hands-on experience in cloud technologies and SDN solutions. He joined the training team at Mirantis in October of 2015 and currently manages content development and delivery of Kubernetes and Istio courses. He is an avid believer in open source technologies and enjoys teaching engineers how to effectively utilize them. For more details, visit https://www.linkedin.com/in/kwanghyolee