Download as PDF, PPTX
Uploaded byKevin Jones
Using NGINX and NGINX Plus as a Kubernetes Ingress
The document discusses the role of NGINX as an ingress controller in Kubernetes, highlighting its capabilities in load balancing, SSL termination, and microservices management. It emphasizes the benefits of Kubernetes for automating deployment and scaling of applications while advocating for more advanced load balancing features through an ingress controller. The presentation includes examples of NGINX configurations and real-time service management using Kubernetes APIs.
More Related Content
Similar to Using NGINX and NGINX Plus as a Kubernetes Ingress
Using NGINX and NGINX Plus as a Kubernetes Ingress
- 1. NGINX as anIngress Controller in Kubernetes Speaker: Kevin Jones Global Product Specialist
- 2.
- 3. 3 “... when Istarted NGINX, I focused on a very specific problem – how to handle more customers per a single server.” - Igor Sysoev, NGINXcreator and founder
- 4. 458 million Total sitesrunning on NGINX Source: Netcraft January 2018 Web Server Survey6
- 5. 62% of the Top10,000 most visited websites Source: : W3Techs Web Technology Survey136
- 6. 54% of the Top100,000 most visited websites Source: : W3Techs Web Technology Survey137
- 7. 40% of all instanceson Amazon Web Services Source: : Sumologic: The State of Modern Applications in AWS Report138
- 8. About NGINX, Inc. •Founded in 2011, NGINXPlus first released in 2013 • VC-backed by enterprise software industry leaders • Officesin SF, London, Cork, Singapore and Moscow • 1,400+ commercial customers • 200+ employees 8
- 9. NGINX for Microservices 9 NGINXhelps ensure microservices are: • Connected • Served • Authenticated • Secured • Cached • Load Balanced • Scaled
- 10. NGINX for APIGateways 10 NGINX provides: • Integration • Security • Request Routing • Optimization • Scalability
- 11. NGINX for HybridCloud & Scaling 11 NGINX Plus can: • Run anywhere • React to environment downtime • Outperformcloud load balancers • Load balance across locations • Scale without additional costs
- 12.
- 13. 13 Kubernetes is anopen-source system for automating deployment, scaling, and management of containerized applications
- 14. Kubernetes makes opseasy… • Run anywhere • Rolling updates • Fault Tolerance • Horizontal Scaling • Load Balancing • YAML… and more! 14
- 15. Built in LoadBalancing
- 16. 1 6 kube-proxykube-proxy hello kube-proxy hello NodePort NodePort NodePort hello Built-inload balancing - NodePort
- 17.
- 18. 18 • Simple andeasy to setup • Limited to layer 4 load balancing • If you need advanced load balancing consider using an Ingress controller so you can bring your own! Built-in load balancing
- 19. Why use anIngress?
- 20. 20 Ingress • Kubernetes resource •Benefits • Externally reachable URLs • Advanced L7 Load Balancing • SSL/TLS • SNI (hostname based routing)
- 21. 21 Ingress Example –Basic
- 22. 22 Ingress Example –URL based routing
- 23. 23 Ingress Example –Host based routing
- 24. 24 Ingress Example –SSL offloading
- 25. 25 Ingress • Pluggableload balancerimplementation: • NGINX/NGINX Plus • GCE HTTP load balancer • HAProxy • … and others - A load balancer is integrated via an Ingress controller that you must deploy
- 26. Deploying NGINX andNGINX Plus as an Ingress Controller
- 27. NGINX and NGINXPlus 27 NGINX • Load balancing w/ SSL/TLS termination • WebSocket and HTTP/2 support • Layer 7 Routing/ Modification NGINX Plus • Session persistence • JWT authentication • 24/7 support, no additional cost • Advanced Monitoring… and more!
- 28. 28 NGINX Ingress Controller •Runs in a container • Well designed, fast and efficient golang script under the hood • Community driven codebase • Available for NGINX and NGINX Plus https://github.com/nginxinc/kubernetes-ingress
- 29.
- 30. 30 My demo today… •URL based routing • Hostname based routing • SSL termination at LB • Support for scaling of replicas at LB via dynamic reconfiguration ../examples/complete-example/
- 31. 31 My demo today… •Café themed application • Two services (URL routing) ◦ /Tea ◦ /Coffee
- 32. Configuring NGINX orNGINX Plus without Ingress
- 33. 33 Data store +template • Register services with a data store (aka etcd or consul) • Template the NGINX configuration and manage NGINX service via CLI (confd or consul template) datastore Services(containers) NGINXOpenSource
- 34. 34 We love APIs! •Services availabilityis managed by kubernetes and availablevia API • Orchestration script can be in any language • NGINX Plus upstreams managed dynamically without configuration reload Services(containers) NGINXPlusAPI KubernetesAPI Orchestration(script)
- 35. 35 Service Discovery ;D •Built in DNS resolver • Control over TTL • Easily Integrates with existing DNS based service discovery tools
- 36.
- 37.
- 38. If you likeNGINX, you’ll love NGINX Plus! nginx.com/developer-license use code: hidden
- 39. Kevin Jones @webopsx Thank You! Learnmore at nginx.com