Protect Kubernetes APIs with Rate Limiting

Описание: Your organization just launched its first app and API in Kubernetes. You’ve been told to expect high traffic volumes (and already implemented autoscaling to ensure NGINX Ingress Controller can quickly route the traffic), but there are concerns that the API may be targeted by a malicious attack. If the API receives a high volume of HTTP requests, as might happen with brute‑force password guessing or DDoS attacks, then both the API and app could be overwhelmed and might even crash.

But you’re in luck! The traffic control technique “rate limiting” is an API gateway use case that limits the incoming request rate to a value typical for real users. You configure NGINX Ingress Controller to implement a rate limiting policy, which prevents the app and API from getting overwhelmed by too many requests. Nice work!

Technologies Used:
◆ NGINX Ingress Controller: https://bit.ly/3vpPkRw
◆ Locust: https://locust.io
◆ Helm: https://helm.sh

Read the companion blog "Protect Kubernetes APIs with Rate Limiting"
⬡ https://bit.ly/3L41jc9

Try this demo for yourself and register today for Microservices March 2022!
⬡ https://bit.ly/3rVAz74
Get Started with NGINX Ingress Controller
⬡ https://bit.ly/35BHoSi
Free eBook: Taking Kubernetes from Test to Production
⬡ https://bit.ly/3HpvaJL

Chapters:
0:00 - Protect Kubernetes APIs with Rate Limiting
0:00 - Part 1: Overwhelm an app and API wth traffic
04:59 - Deploy two NGINX Ingress Controllers
08:16 - Implement rate limiting on the NGINX Ingress Controller serving the API
17:21 - NGINX.COM/MM Microservices March 2022