explaingit

kubernetes/ingress-nginx

★ 19,495GoAudience · ops devopsComplexity · 4/5MaintainedLicenseSetup · hard

TLDR

A Kubernetes tool that routes web traffic to your services using NGINX. Now retired; existing deployments still work but new projects should use Gateway API instead.

Mindmap

mindmap
  root((repo))
    What it does
      Routes web traffic
      Syncs NGINX config
      Watches Kubernetes rules
    Tech stack
      Go
      NGINX
      Kubernetes
      Helm
    Use cases
      Direct traffic to services
      Load balance requests
      Manage routing rules
    Status
      Retired project
      No new releases
      Existing deployments work
    Deployment
      Helm charts
      Container images
      Kubernetes native

Things people build with this

USE CASE 1

Route incoming web traffic to the correct service in your Kubernetes cluster.

USE CASE 2

Automatically update NGINX configuration when you change routing rules in Kubernetes.

USE CASE 3

Load balance requests across multiple instances of your services.

USE CASE 4

Manage SSL/TLS certificates and HTTPS routing for services running in Kubernetes.

Tech stack

GoNGINXKubernetesHelm

Getting it running

Difficulty · hard Time to first run · 1h+

Requires running Kubernetes cluster, NGINX configuration, and Helm chart deployment with multiple components.

Use freely for any purpose including commercial. Keep the notice and disclose changes to the patent grant.

In plain English

The Ingress NGINX Controller was a tool for Kubernetes, a platform for running and managing containerized applications, that handled routing web traffic into those applications. When you run multiple web services inside a Kubernetes cluster, you need something to act as a "front door" that receives requests from the internet and directs them to the right service. This controller used NGINX, a widely-used web server and reverse proxy, to do exactly that: it watched for routing rules defined in your Kubernetes configuration and automatically kept NGINX in sync with those rules. Important note: this project is now retired. Active development has stopped, and after March 2026 there will be no more releases, bug fixes, or security patches. Anyone not already using it is advised to use a Gateway API implementation instead. Existing deployments will continue to work, and existing Helm charts and container images remain available. If you were maintaining a Kubernetes cluster and needed web traffic routed to your services, this was the standard tool. The tech stack is Go, NGINX, Kubernetes, and it was deployable via Helm charts.

Copy-paste prompts

Prompt 1
Show me how to set up Ingress NGINX Controller in my Kubernetes cluster using Helm.
Prompt 2
How do I define routing rules for my services using Kubernetes Ingress resources with NGINX?
Prompt 3
What are the key configuration options for Ingress NGINX Controller and how do I customize them?
Prompt 4
How does Ingress NGINX Controller watch and sync changes from my Kubernetes configuration to NGINX?
Open on GitHub → Explain another repo

Generated 2026-05-18 · Model: sonnet-4-6 · Verify against the repo before relying on details.