wxingress¶
The ingress-nginx successor you can drop in. wxingress serves your Ingresses, your
nginx.ingress.kubernetes.io/* annotations and your ingress-nginx ConfigMap as they are. It is built on
NGINX Ingress Controller's core, runs no Lua, and adds the Gateway API.
Install Migrate from ingress-nginx
Made by WX-ONE and WizardTales¶
wxingress is officially maintained by WizardTales and runs the ingress of the WX-ONE cloud platform. That is our commitment: it stays open source under the EUPL-1.2, and since we depend on it ourselves, its development is secured. Donations are still very welcome and go exclusively into its development: sponsor wxingress.
Commercial support
WizardTales offers support packages for production use: the fast release channel (targeted fixes for critical vulnerabilities from the WX-ONE emergency response team, ahead of the official release) for €1,000 per month and the emergency support desk (8×5, prioritised, 24×7 on request, including the fast release channel) for €3,000 per month, each per legal entity. Order by email to support-ingress@wx1.de. Details
Why it exists¶
The Kubernetes project retired ingress-nginx in March 2026. Its Ingresses did not go away: they carry ingress-nginx's annotations, depend on its defaults (5 s connect timeout, buffering off, three upstream retries, HSTS) and are written by Helm charts that will keep writing them for years.
wxingress is a fork of NGINX Ingress Controller (NIC) that teaches NIC ingress-nginx:
- It serves the IngressClass of controller
k8s.io/ingress-nginxand Ingresses without a class. - It reads ingress-nginx's annotations and ConfigMap keys and translates them into NIC's configuration.
- With
-ingress-nginx-defaultsit uses ingress-nginx's defaults wherever an Ingress sets nothing. - Its admission webhook refuses what ingress-nginx's refuses.
- It exports ingress-nginx's Prometheus metrics, under ingress-nginx's names.
A request gets the same answer from wxingress as from ingress-nginx. The project checks this with a corpus of 97 Ingresses from production clusters and popular Helm charts, probed 2562 ways. The details are in Testing and benchmarks.
What you get¶
-
Drop-in compatibility
Annotations, ConfigMap keys, IngressClass, defaults, admission checks and metrics of ingress-nginx. Unsupported annotations show up as Warning events on the Ingress, never silently. Compatibility
-
No Lua, less CPU
About 4 times the HTTP requests per second of ingress-nginx, half the CPU per HTTPS request and half the memory under load. Endpoint changes need no reload and almost no controller CPU.
-
Gateway API
Gateways with HTTPRoute, GRPCRoute, TLSRoute, TCPRoute and UDPRoute on the same controller. The Gateway API semantics (attachment, conflicts, status) come from NGINX Gateway Fabric. Tested against the conformance suite; not yet in our production. Gateway API
-
All of NGINX Ingress Controller
VirtualServer, VirtualServerRoute, TransportServer, Policy, GlobalConfiguration and the
nginx.org/*annotations, with an open-source NGINX.
Performance¶
Same node, same backends, same 97 Ingresses, each controller installed fresh as a hostPort DaemonSet with four NGINX workers:
| ingress-nginx 1.15.1 | rke2-ingress-nginx 1.12.6 | wxingress | |
|---|---|---|---|
| HTTP requests/s | 39 156 | 62 145 | 161 832 |
| HTTP p50 / p99 | 1.68 / 4.69 ms | 0.93 / 4.54 ms | 0.38 / 0.60 ms |
| HTTPS requests/s | 30 960 | 37 766 | 63 629 |
| CPU per HTTPS request | 141 µs | 120 µs | 63 µs |
| Memory at rest / under load | 132 / 246 MiB | 134 / 284 MiB | 128 / 135 MiB |
| Controller CPU during endpoint churn | 28.8 s | 42.3 s | 0.16 s |
| { .hero-numbers } |
The method, the raw numbers and where the difference comes from are in Testing and benchmarks.
The one exception: Lua¶
ingress-nginx ran Lua: in its balancer, its metrics, and in snippets that users wrote. wxingress has no
Lua. Snippets that only contain NGINX directives keep working once snippets are enabled. Snippets with
access_by_lua_block, content_by_lua_block and the like need a rewrite in
njs, NGINX's JavaScript, which wxingress ships. The
Lua to njs guide shows the patterns, with a complete example.