Control Kubernetes Ingress and Egress Together with NGINX
Nginx
562 views
27 slides
Feb 23, 2021
Slide 1 of 27
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
About This Presentation
Join our resident Kubernetes and modern apps experts in a discussion of the challenges of Kubernetes traffic management in today’s technology landscape. While Kubernetes Ingress gets most of the attention, how you handle egress traffic is just as important. Egress isn’t just about traffic leavin...
Join our resident Kubernetes and modern apps experts in a discussion of the challenges of Kubernetes traffic management in today’s technology landscape. While Kubernetes Ingress gets most of the attention, how you handle egress traffic is just as important. Egress isn’t just about traffic leaving a cluster, either, but also concerns traffic among managed and unmanaged services within the cluster. We demo a solution using NGINX Service Mesh and NGINX Ingress Controller to control egress from the cluster and between NGINX Service Mesh and unmanaged services. Whether you’re new to modern application architectures, or looking to improve your current microservices deployment, this webinar is for you.
Join this webinar to learn:
* Solutions to common challenges when managing traffic in Kubernetes
* How to control both ingress and egress in a single configuration
* Which solutions from NGINX can best serve your needs, depending on your requirements
* About NGINX Service Mesh and NGINX Ingress Controller with live demos
Size: 9.96 MB
Language: en
Added: Feb 23, 2021
Slides: 27 pages
Slide Content
Control Ingress and Egress traffic in Kubernetes with NGINX Amir Rawdat Technical Marketing Engineer, NGINX
Agenda Common challenges with managing traffic inside Kubernetes Moving away from annotations with NGINX Ingress Resources Enhancing troubleshooting and logging Controlling ingress/ egrees traffic with a single configuration Enabling agile deployments and maintaining uptime Going even further with NGINX Service Mesh Q&A
Kubernetes becoming platform for developing, testing and running applications Applications are becoming ephemeral by nature This brings limitations to Layer 4 Kubernetes Networking NGINX provides L5-7 networking policies as an alternative to IP addresses Cybersecurity is an ever-growing, ever-complicating field Traditional firewalls and anti virus security is irrelevant or obsolete. Data breaches on the rise and will continue to rise throughout 2021. What we see in the market Kubernetes-centric perspective Source: information Example Adoption of managed and commercial Kubernetes platforms We see rapid adoption of OpenShift and Rancher in the private cloud space EKS and GKE adoption in public cloud
My Favorite Article Titles But K8s Adoption Brings Complexity “ Let’s Use Kubernetes!”Now You Have 8 Problems” ”Will Complexity Kill Kubernetes?” “Has Kubernetes Already Become To Unnecessarily Complex for Enterprise IT?” ”Why Kubernetes Networking Is Hard – And What You Can Do About It”
What’s missing in K8s and What do you really want and need from a mesh? Networking: K8s, L4-L7 K8s, and CNI, provides L4 servicing – IP endpoints Many, complex options https://kubernetes.io/docs/concepts/cluster-administration/networking/ L7 Traffic Management is missing Policy-based routing Service-level access control SSL/ mTLS enforcement Integrated Ingress/Egress Enter: KIC + Service Mesh – Taking control of Kubernetes networking
Controlling ingress/egress traffic with NGINX KIC CONFIDENTIAL
Problems with Ingress Resources Confidential – Do Not Distribute Kubernetes Ingress resources are limited to basic SSL/TLS and HTTP load balancing Configuration can be further customized with Annotations, ConfigMaps , and templates Global scoped and not fine grained Very error prone Difficult to pint point validation errors
NGINX Ingress Resources Confidential – Do Not Distribute Native Type-Safe Configuration Provides advanced app delivery features with native Kubernetes workflow. Increased modularity and reusability Finer grained multi-tenancy with NGINX cross- namespacing
Protecting your Kubernetes Apps from Vulnerabilities and Attacks CONFIDENTIAL
Consolidating the NGINX Ingress Controller with a battle tested WAF Configuration is fully managed by the Kubernetes API Leverage Kubernetes RBAC to securely delegate WAF configurations to a dedicated DevSecOps team Block unrecognized threats with user defined signatures WAF CONFIDENTIAL Blocking Threats with NGINX App Protect
CONFIDENTIAL Blocking Threats with NGINX App Protect Secure perimeter for your applications in Kubernetes
Advanced App Centric Configuration Confidential – Do Not Distribute
Going Even Further with NGINX Service Mesh CONFIDENTIAL
Data Plane Control Plane
Bookinfo demo Confidential – Do Not Distribute
What Does A Service Mesh Do? Service Mesh controls communications between pods and external apps Secure Traffic End-to-end encryption (Mutual TLS / mTLS ), ACLs Manage All Service Traffic Load Balance, Circuit breaker, B|G, Rate Limiting… Orchestration Injection and sidecar management, K8s API integration Measure Traffic Generate transaction traces and real-time monitoring
When Am I Ready For A Service Mesh? You have a mature, fully-automated CI/CD pipeline ( GitOps -enabled) You are fully invested in Kubernetes You are deploying frequently to production (at least once per day) You have a zero-trust production environment (so need mTLS ) You need/want additional visibility of container traffic interaction
Get Started with the NGINX Ingress Controller -- https://github.com/nginxinc/kubernetes-ingress Get a free trial of NGINX Plus Ingress Controller -- https://www.nginx.com/free-trial-request-nginx-ingress-controller/ OPEN TALK: Securing and Managing K8s Apps with Ease: NGINX Service Mesh Download NGINX Service Mesh for free -- https://downloads.f5.com Get Started Today !!