Rate Limiting and IP Whitelisting
What you'll learn: How to protect your Kubernetes services by controlling traffic flow and restricting access based on source IPs using Ingress annotations.
The Core Idea
Rate limiting and IP whitelisting are traffic control policies you implement at the Ingress level to protect your applications. Rate limiting restricts how many requests a client can make in a given time period (like a bouncer counting how many times someone enters a club per hour). IP whitelisting only allows traffic from specific, trusted IP addresses (like a guest list at an exclusive event).
Both features are configured using Ingress annotations—metadata you add to your Ingress resource that instructs the Ingress Controller how to handle traffic.
Implementing These Controls
Since you're already familiar with Ingress annotations from earlier lessons, you know these are key-value pairs in your Ingress YAML. For NGINX Ingress Controller (which you installed in lesson 1222), rate limiting typically uses annotations like:
nginx.ingress.kubernetes.io/limit-rps— limits requests per second per IPnginx.ingress.kubernetes.io/limit-connections— limits concurrent connections
For IP whitelisting, you'd use:
nginx.ingress.kubernetes.io/whitelist-source-range— comma-separated list of allowed CIDR blocks
These annotations work alongside your existing host-based routing and path rules—they simply add an extra layer of traffic control before requests reach your Services.
Why This Matters
Without these controls, a single misbehaving client could overwhelm your application, or malicious actors from anywhere could attempt attacks. Rate limiting prevents abuse, and IP whitelisting ensures only trusted networks (like your office or partner systems) can access sensitive endpoints.
Key Takeaway: Use Ingress annotations to implement rate limiting and IP whitelisting, adding critical traffic control without changing your application code or Service definitions.