ingress-nginx — Kubernetes NGINX Ingress Controller

What it is

ingress-nginx is the community-maintained Kubernetes ingress controller built on NGINX. It translates Kubernetes Ingress and Gateway API resources into NGINX configuration, providing HTTP/S load balancing, TLS termination, path-based routing, and rate limiting for cluster services. It is the most widely deployed ingress controller in the Kubernetes ecosystem.

The controller targets platform engineers and DevOps teams running Kubernetes clusters who need to expose services to external traffic. It works on every major cloud provider and on-premises Kubernetes distributions.

How it saves time or tokens

ingress-nginx eliminates manual NGINX configuration management. Instead of writing and reloading NGINX configs, you declare routing rules as Kubernetes Ingress resources, and the controller generates and applies the configuration automatically. Annotations provide fine-grained control over rate limiting, CORS, SSL redirects, and upstream behavior without touching NGINX config files directly.

How to use

1. Install with the official Helm chart:

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx \
  -n ingress-nginx --create-namespace

1. Create an Ingress resource for your service:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: my-app
  annotations:
    nginx.ingress.kubernetes.io/ssl-redirect: 'true'
spec:
  ingressClassName: nginx
  rules:
  - host: app.example.com
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: my-app-svc
            port:
              number: 80

1. Apply the resource and verify the external IP: kubectl get ingress my-app.

Example

Rate limiting and CORS configuration via annotations:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: api-ingress
  annotations:
    nginx.ingress.kubernetes.io/rate-limit: '100'
    nginx.ingress.kubernetes.io/rate-limit-window: '1m'
    nginx.ingress.kubernetes.io/enable-cors: 'true'
    nginx.ingress.kubernetes.io/cors-allow-origin: 'https://frontend.example.com'
spec:
  ingressClassName: nginx
  rules:
  - host: api.example.com
    http:
      paths:
      - path: /v1
        pathType: Prefix
        backend:
          service:
            name: api-svc
            port:
              number: 8080

Related on TokRepo

• AI Tools for DevOps — DevOps tools for Kubernetes deployment and cluster management
• AI Tools for Monitoring — Monitoring tools for tracking ingress controller metrics

Common pitfalls

• The community ingress-nginx and the NGINX Inc ingress controller are different projects. Ensure you install the community version from kubernetes.github.io/ingress-nginx.
• Annotation typos fail silently. A misspelled annotation key is ignored, and the default behavior applies without warning.
• TLS certificates must be stored as Kubernetes secrets and referenced in the Ingress spec. Missing or expired certificates cause 502 errors, not helpful error messages.
• Always check the official documentation for the latest version-specific changes and migration guides before upgrading in production environments.
• For team deployments, establish clear guidelines on configuration and usage patterns to ensure consistency across developers.