nginx/kubernetes-ingress

Features

• TCP and UDP Listeners - Defines ports, protocols, and IP addresses for TCP, UDP, and HTTP traffic to enable comprehensive load balancing.
• Configuration-Driven Templating Engines - Renders NGINX configuration files by merging user-defined metadata with logic-driven templates.
• Configuration Translation - Translates Kubernetes API objects and annotations into proxy configuration files using predefined templates.
• Dynamic Configuration Updates - The NGINX Ingress Controller applies infrastructure changes without reloading the process to prevent memory spikes and connection drops.
• Global Controller Configurations - Provides centralized management of system-wide settings like timeouts and log formats.
• Annotation-Driven Configurations - Enables granular control over proxy behavior, such as rate limiting and SSL settings, using Kubernetes resource annotations.
• Ingress Class Selectors - Implements resource isolation by identifying which routing rules a specific controller instance should manage.
• Live Configuration Reloads - Applies infrastructure changes to the proxy without restarting the process to maintain long-lived client connections.
• TLS Termination - The NGINX Ingress Controller decrypts incoming HTTPS traffic using certificates stored in secrets before forwarding to backends.
• Health-Checked Routers - Probes backend services to verify availability and removes unhealthy instances from the load balancing pool.
• Content-Aware Routing Rules - Directs incoming requests to internal services by inspecting request headers, paths, and payloads.
• Revision Traffic Splits - Distributes network traffic across multiple backend services to enable canary or blue-green releases.
• URI Routing and Redirections - Changes the request URI before it is passed to the backend to ensure compatible routing.
• Web Application Firewalls - Protects applications from common web exploits and attacks using rule-based inspection and security policy bundles.
• Resource Metadata Mappings - Maps Kubernetes resource metadata tags to low-level proxy directives for granular request handling customization.
• Canary and Proportional Routing - Routes a percentage of traffic to a new service version using headers or weights for canary testing.
• Metrics Exporters - The NGINX Ingress Controller exposes internal data and load balancer metrics in a format compatible with external monitoring tools.
• HTTP Health Probes - Continually tests backend service availability to dynamically remove unhealthy pods from the load balancing pool.
• Prometheus Metrics Exporters - The NGINX Ingress Controller exposes operational data and performance metrics via a dedicated endpoint for Prometheus monitoring.
• Request Logging - The NGINX Ingress Controller records detailed information about client requests using customizable log formats.
• Path-Based Routing - Maps request URIs to backend services using exact, regex, or prefix matching.
• Custom Signatures - Allows the creation of user-defined security signatures to detect and block specific traffic patterns.
• Dynamic Module Loading - Extends the request pipeline by loading external binary modules into the container image at runtime.
• Regex-Based Route Matching - Matches request paths against regular expressions to route traffic to specific backend services.
• Configuration Rollbacks - Ensures system stability by validating new configurations and restoring the previous state if errors occur.
• Annotation-Driven - Adds custom configuration directives by modifying templates to process user-defined annotations.
• Routing Policy Resources - Defines advanced routing rules and server behaviors using custom Kubernetes resource specifications.
• Custom Resource Status Management - The NGINX Ingress Controller updates status fields of resources with current state, validation messages, and external endpoints.
• Configuration Validations - The NGINX Ingress Controller checks the validity of resource annotations and rejects invalid configurations to prevent instability.
• Label-Based Pod Routing - Routes requests to a collection of backend resources based on matching Kubernetes labels.
• Load Balancing Algorithms - Distributes requests using specialized methods like least-time to optimize response times.
• Request Rate Limiting - Controls the volume of requests processed per key to prevent backend service exhaustion.
• Proxy Configuration Injections - Allows the insertion of raw server configuration directives to implement advanced behaviors not covered by standard APIs.
• SNI-Based TLS Routers - Routes incoming encrypted TLS connections to different virtual hosts based on the Server Name Indication extension.
• Real-Time Traffic Dashboards - The NGINX Ingress Controller displays real-time activity and health metrics for applications via a visual dashboard.
• Session Persistence - Implements mechanisms to maintain user session consistency via sticky routes or cookies during traffic shifting.
• Proxy Resource Tuning - Optimizes server-wide performance by adjusting timeouts, buffer sizes, and body limits.
• Proxy Content Caches - The NGINX Ingress Controller stores responses from backend services to serve subsequent requests faster and reduce upstream load.
• Custom Header Injections - Adds custom headers to the server response for metadata or security purposes.
• TLS Passthroughs - The NGINX Ingress Controller routes encrypted traffic directly to backend services without decrypting it at the edge.
• TCP and UDP Forwarders - Routes raw TCP and UDP datagrams between public ports and internal backend services.
• Controller Instance Isolation - Ensures controller instances only manage resources assigned to their specific class identifier for isolation.
• Network-Based Access Controls - The NGINX Ingress Controller blocks or permits traffic based on CIDR ranges to control network access.
• Reusable Policy Templates - Creates shared, reusable configuration templates for access control and rate limiting across multiple resources.
• HTTP Delegated Authentications - Forwards requests to an external authentication server to determine if a client is authorized.
• Basic Authentication - Requires valid HTTP Basic authentication credentials before granting access to requested services.
• DoS Attack Defenses - The NGINX Ingress Controller prevents denial-of-service attacks by integrating a protection module into the controller image.
• Policy Configurations - The NGINX Ingress Controller defines behavioral rules for detecting and mitigating DoS attacks via policy resources.
• HTTP Request and Response Modifiers - Modifies request URIs and adds response headers in real time through configurable rules.
• TLS Certificate Management - The NGINX Ingress Controller integrates with external managers to automatically issue and renew certificates for virtual servers.
• API Key Authentication - Validates requests by verifying a required API key provided in a header or query parameter.
• Mutual TLS Authentication - The NGINX Ingress Controller enforces mutual TLS by validating client certificates during the handshake process.
• OpenID Connect Support - Authenticates users by integrating an OpenID Connect provider to manage identity and access control.
• JWT Token Validators - Verifies requestor identity by validating JSON Web Tokens and API keys at the network edge.
• TLS Certificate Management - The NGINX Ingress Controller assigns a default TLS secret to handle termination for resources lacking a defined host.
• JWT Authentications - Verifies the identity of a requestor by validating signed JSON Web Tokens.
• Configuration Templates - Allows overriding the default logic used to generate NGINX configuration files via custom templates.
• Security Policy Compilation - Transforms security policy files into compiled bundles to reduce resource impact and avoid proxy reloads.
• Routing Extension Modules - Extends the request pipeline by integrating additional binary modules into the container image.
• Namespace Scoped Operations - Limits a controller instance to processing resources within specific namespaces for security and isolation.
• Upstream Health Monitoring - The NGINX Ingress Controller exposes a JSON endpoint that reports the health count of upstream pods for services.
• Distributed Tracing - The NGINX Ingress Controller tracks request flows across microservices to analyze latency and troubleshoot distributed systems.
• Server Status Monitors - The NGINX Ingress Controller reports basic metrics and protection health via a web interface or API.
• HTTP Redirects - The NGINX Ingress Controller forces insecure requests to use an encrypted connection by returning a TLS redirect code.

Star history