Getting traffic into a cluster is one of the first tasks most of us undertake after spinning K8s, but this seemingly simple task can often appear daunting -- both in terms of ingress options and implementation of the chosen solution. Daniel will take us on a tour of Ambassador, the Kubernetes native API gateway, the motivations for building it, reasons the Datawire team built it upon the Envoy Proxy, and and a quick tour of an example deployment.

1. Ambassador (@getambassadorio):
Open Source Kubernetes Edge Gateway
Daniel Bryant
@danielbryantuk

2. Lessons learned from a childhood misspent
• The system’s “edge” is super important
• Systems with more things require more
collaboration/coordination
• Plug and play (extensibility) enables a
rapid start, but support customisation
30/11/2018 @danielbryantuk

3. @danielbryantuk
• Independent Tech Consultant, Product Architect at Datawire
• Architecture, DevOps, Java, microservices, cloud, containers
• Continuous Delivery (CI/CD) advocate
• Leading change through technology and teams
30/11/2018 @danielbryantuk
bit.ly/2jWDSF7
oreil.ly/2E63nCR

4. Why (did we build Ambassador)?
30/11/2018 @danielbryantuk

5. Common challenges when adopting k8s
• Getting traffic into the cluster – handling the edge
• Kubernetes Ingress (stuck in beta)
• Default often NGINX (but which one? ingress-nginx, kubernetes-ingress etc)
• Lots of variation in annotations
• Coordinating (human) updates to ingress config
• Avoiding contention with a single-source file
• Easy implementation of shadowing, canarying etc
30/11/2018 @danielbryantuk

6. Working with the edge should be easier…
30/11/2018 @danielbryantuk

7. Living on the edge: “north/south” traffic
30/11/2018 @danielbryantuk

8. Living on the edge: “north/south” traffic
30/11/2018 @danielbryantuk

9. 30/11/2018 @danielbryantuk

10. 30/11/2018 @danielbryantuk
https://bit.ly/2SjmlYN

11. What we wanted
30/11/2018 @danielbryantuk

12. Focusing on ingress: “north/south” traffic
30/11/2018 @danielbryantuk

13. How (to use Ambassador)
30/11/2018 @danielbryantuk

14. 30/11/2018 @danielbryantuk

15. 30/11/2018 @danielbryantuk

16. 30/11/2018 @danielbryantuk

17. 30/11/2018 @danielbryantuk

18. 30/11/2018 @danielbryantuk
https://admiralty.io/blog/kubernetes-custom-resource-controller-and-operator-development-tools/

19. 30/11/2018 @danielbryantuk

20. What (are the use cases)?
30/11/2018 @danielbryantuk

21. Majority focus on simple ingress
30/11/2018 @danielbryantuk

22. 30/11/2018 @danielbryantuk
https://www.appdirect.com/blog/evolution-of-the-appdirect-
kubernetes-network-infrastructure

23. 30/11/2018 @danielbryantuk

24. Plugins…
30/11/2018 @danielbryantuk

25. 30/11/2018 @danielbryantuk

26. Authentication
30/11/2018 @danielbryantuk
https://www.getambassador.io/user-guide/auth-tutorial https://www.getambassador.io/user-guide/oauth-oidc-auth

27. Distributed tracing
30/11/2018 @danielbryantuk
https://bit.ly/2zw6lvy
https://bit.ly/2TUEbmF

28. Rate limiting
30/11/2018 @danielbryantuk
https://blog.getambassador.io/rate-limiting-for-api-gateways-892310a2da02

29. Lyft’s ratelimit service
30/11/2018 @danielbryantuk

30. The Future
30/11/2018 @danielbryantuk

31. Somewhere in a parallel world…
30/11/2018 @danielbryantuk

32. 30/11/2018 @danielbryantuk

33. Service mesh all-the-things
30/11/2018 @danielbryantuk

34. Wrapping up…
30/11/2018 @danielbryantuk
https://kubedex.com/ingress/

35. Thanks for listening…
Twitter: @danielbryantuk
Email: daniel.bryant@tai-dev.co.uk
Writing: https://www.infoq.com/profile/Daniel-Bryant
Talks: https://www.youtube.com/playlist?list=PLoVYf_0qOYNeBmrpjuBOOAqJnQb3QAEtM
30/11/2018 @danielbryantuk
bit.ly/2jWDSF7
bit.ly/2BTjpir

36. Bonus
30/11/2018 @danielbryantuk

37. 30/11/2018 @danielbryantuk