kubernetes/ingress-nginx

Analysis updated 2026-05-18

★ 19,499GoAudience · ops devopsComplexity · 4/5LicenseSetup · hard

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

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

Click or tap to explore — scroll the page freely

What do people build with it?

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.

What is it built with?

GoNGINXKubernetesHelm

How does it compare?

	kubernetes/ingress-nginx	yudai/gotty	dariubs/gobooks
Stars	19,499	19,470	19,404
Language	Go	Go	Go
Setup difficulty	hard	easy	easy
Complexity	4/5	2/5	1/5
Audience	ops devops	ops devops	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get 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?

Frequently asked questions

What is ingress-nginx?

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.

What language is ingress-nginx written in?

Mainly Go. The stack also includes Go, NGINX, Kubernetes.

What license does ingress-nginx use?

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

How hard is ingress-nginx to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is ingress-nginx for?

Mainly ops devops.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Scan in gitsafehub Deploy in gitdeployhub kubernetes on gitmyhub

Verify against the repo before relying on details.