awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
kubernetes avatar

kubernetes/ingress-nginxArchived

0
View on GitHub↗
19,492 stars·8,566 forks·Go·Apache-2.0·33 viewskubernetes.github.io/ingress-nginx↗

Ingress Nginx

This project is a Kubernetes Ingress Controller that functions as a layer 7 traffic router and NGINX reverse proxy. It serves as a secure network gateway, directing external HTTP and HTTPS traffic to backend services within a cluster based on declarative routing rules.

The controller acts as a TLS termination gateway to secure traffic and integrates with Prometheus to expose request metrics and latency data for cluster monitoring. It supports canary deployment workflows by implementing weight-based traffic splitting between different versions of a service.

The system manages external access and multi-service routing through hostname and path-based rules. It utilizes a template-driven configuration process that synchronizes with cluster resources, employing leader election for high availability and hot-reloading to apply updates without disrupting active connections.

Features

  • Ingress Controllers - Manages external access to Kubernetes services through load balancing and name-based virtual hosting.
  • Ingress Gateways - Provides a single entry point and secure network gateway for all external traffic entering the Kubernetes cluster.
  • Go Template Rendering - Uses Go's text/template engine to dynamically render Nginx routing configurations.
  • Configuration-Driven Templating Engines - Generates Nginx configuration files by processing Go templates based on cluster resource data.
  • Dynamic Resource Watching - Employs Kubernetes informers to watch for resource changes and trigger configuration updates.
  • Reverse Proxy Configurations - Configures NGINX as a reverse proxy to handle load balancing and routing for Kubernetes services.
  • Layer 4 and Layer 7 Proxies - Operates as an application-layer proxy to route requests based on hostnames and paths.
  • Layer 7 Traffic Routers - Directs application-layer requests to backend services using hostname and path-based rules.
  • Request Routing - Directs incoming web requests to internal services using predefined hostnames and path-based matching rules.
  • Configuration Generators - Compiles Kubernetes resource data into unified Nginx configuration files.
  • TLS Termination - Terminates TLS connections at the ingress layer to secure traffic before it enters the cluster.
  • Proxy Traffic Management - Directs external network traffic to internal services using a high-performance reverse proxy and load balancer.
  • Traffic Routing - Routes HTTP and HTTPS traffic to multiple backend services based on hostnames and custom rules.
  • Reverse Proxies - Implements a high-performance reverse proxy using Nginx to handle load balancing and request routing.
  • Hot Reloading - Provides the capability to apply configuration changes immediately without restarting the process.
  • Signal-Based Reloading - Applies configuration changes by sending a reload signal to Nginx to avoid dropping connections.
  • Canary Deployment Controllers - Manages incremental traffic shifts for API updates to safely perform canary deployments.
  • Leader Election - Uses distributed locking to ensure only one controller instance manages the configuration state.
  • Annotation-Driven Configurations - Parses Kubernetes Ingress annotations to inject specific Nginx directives for rate limiting and SSL.
  • Weighted Traffic Splitting - Implements canary rollouts by distributing traffic between service versions using weighted load balancing.
  • Ingress Annotation Injections - Implements custom Nginx configuration injection via Kubernetes Ingress resource annotations.
  • Kubernetes Monitors - Exposes NGINX request counts and latency metrics for Kubernetes cluster performance monitoring via Prometheus.
  • Lua Scripting Extensions - Utilizes embedded Lua scripts for dynamic L7 request processing and routing logic.
  • Networking - Ingress controller using NGINX as a reverse proxy.

Star history

Star history chart for kubernetes/ingress-nginxStar history chart for kubernetes/ingress-nginx

How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI

Projects sharing features with Ingress Nginx

These projects share indexed features with Ingress Nginx. Shared tags can include platform or build tooling; verify the primary use case before treating a result as a replacement.
  • alibaba/higressalibaba avatar

    alibaba/higress

    7,558View on GitHub↗

    Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It provides a centralized system for routing, securing, and optimizing traffic directed toward large language models, AI agents, and microservice architectures. The project distinguishes itself through deep AI orchestration, including the ability to host and manage Model Context Protocol servers that transform REST APIs into tools for AI agents. It features specialized AI infrastructure for model request proxying, protocol translation across multiple providers, and semantic-based c

    Goai-gatewayai-nativeapi-gateway
    View on GitHub↗7,558
  • weaveworks/flaggerweaveworks avatar

    weaveworks/flagger

    5,362View on GitHub↗

    Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive delivery. It functions as a controller that monitors custom resource definitions to orchestrate complex release strategies, including canary, blue/green, and A/B testing. By continuously reconciling the desired cluster state with the actual environment, it ensures that deployments adhere to defined specifications while managing the underlying infrastructure required for traffic routing. The project distinguishes itself through a sophisticated metric-driven analysis loop that eval

    Go
    View on GitHub↗5,362
  • kubernetes-sigs/gateway-apikubernetes-sigs avatar

    kubernetes-sigs/gateway-api

    2,661View on GitHub↗

    The Gateway API is a standardized set of resources for routing HTTP, gRPC, and TCP traffic into and within Kubernetes clusters. It serves as a framework for defining load balancer listeners and routing rules for both Layer 4 and Layer 7 protocols, acting as a specification for ingress and service mesh traffic interfaces. The project utilizes a role-oriented configuration that separates infrastructure provisioning from routing logic. It implements a class-based provider selection system to match requested infrastructure to specific controller implementations and employs a conformance-driven sp

    Gogateway-apik8s-sig-networkkubernetes
    View on GitHub↗2,661
  • kubernetes/ingress-gcekubernetes avatar

    kubernetes/ingress-gce

    1,301View on GitHub↗

    This project is a Kubernetes ingress controller that manages external traffic routing by integrating directly with Google Cloud load balancing infrastructure. It functions as a controller that continuously reconciles the desired state of cluster ingress definitions with the actual configuration of cloud-native load balancers. The controller automates the provisioning of static or ephemeral IP addresses and configures load balancers to distribute network requests across multiple availability zones. It employs declarative mapping to translate abstract service definitions into concrete cloud inf

    Gogoogleingressk8s
    View on GitHub↗1,301
Compare all 30 related projects→

Frequently asked questions

What does kubernetes/ingress-nginx do?

This project is a Kubernetes Ingress Controller that functions as a layer 7 traffic router and NGINX reverse proxy. It serves as a secure network gateway, directing external HTTP and HTTPS traffic to backend services within a cluster based on declarative routing rules.

What are the main features of kubernetes/ingress-nginx?

The main features of kubernetes/ingress-nginx are: Ingress Controllers, Ingress Gateways, Go Template Rendering, Configuration-Driven Templating Engines, Dynamic Resource Watching, Reverse Proxy Configurations, Layer 4 and Layer 7 Proxies, Layer 7 Traffic Routers.

Which projects share features with kubernetes/ingress-nginx?

Projects with overlapping indexed features include: alibaba/higress — Higress is an AI API gateway and cloud-native traffic manager that functions as a Kubernetes ingress controller. It… weaveworks/flagger — Flagger is a Kubernetes operator designed to automate the lifecycle of application deployments through progressive… kubernetes-sigs/gateway-api — The Gateway API is a standardized set of resources for routing HTTP, gRPC, and TCP traffic into and within Kubernetes… kubernetes/ingress-gce — This project is a Kubernetes ingress controller that manages external traffic routing by integrating directly with… bunkerity/bunkerweb — BunkerWeb is a containerized suite of infrastructure tools that functions as a cloud-native web application firewall… dotnet/yarp — Yarp is a .NET HTTP reverse proxy toolkit and framework used to build applications that route network traffic to…