No. 18 of 27 ·Kubernetes Ingress Controllers

OpenNJet Ingress Controller

Self-hosted

Freedom report

One barScore 5.3

Free tierNo free tier on record
Open codeNo open-source code on record
Runs widely0 of 6 device platforms
DocumentedPlans, terms and facts published

OpenNJet Ingress Controller is ranked #18 of 27 in Kubernetes ingress controllers on Freedom251. It runs on Self-hosted.

Compared on Kubernetes ingress controllers

Free plan: Yes
Ingress API model: both
Canary routing: Yes
Deployment model: self-hosted

Best OpenNJet Ingress Controller alternatives

See all 20

Two bars ngrok Free tier No. 1$10/mo6.6 Two bars Kusk Gateway Free tier No. 2Free6.5 Two bars BFE Ingress Controller Free tier No. 3Free6.4 Two bars Traefik Proxy Free tier No. 4Free6.4 One bar agentgateway Free tier No. 5Free6.3 One bar HAProxy Ingress Free tier No. 6Free6.3

The record

Purpose: OpenNJet KIC is a Kubernetes Ingress Controller built on the dynamic capabilities and performance of the OpenNJet proxy.
Traffic management: It provides dynamic locations, host and path routing, load balancing, dynamic upstreams, canary releases, TLS termination and SNI, TCP and UDP proxying, and WebSocket support.
Ingress scaling: Its sharding mechanism assigns Ingress and VirtualServer resources to KIC instances by IngressClass to reduce the configuration load handled by each KIC type.
ADC integration: KIC can register service domains, application pools, and virtual servers with an ADC so the ADC can act as a front-end load balancer.
Dynamic TCP and UDP: TCP and UDP proxy configuration can be updated dynamically without reloading OpenNJet.
HTTP headers: KIC can modify client request headers and proxied-service response headers, including custom and HTTP-standard headers.
Cross-namespace routing: Ingress and VirtualServer configurations can route across Kubernetes namespaces.
Access logs: Access-log settings, including whether logging is enabled and the log file path, can be set per application or globally through an njet-config ConfigMap; per-application settings take priority.
Health checks: TransportServer resources support active TCP health checks that can take backends online or offline based on whether the configured port responds.
Worker configuration: A ConfigMap can dynamically change the NJet worker-process count, with allowed values from 1 to 512 and an automatic CPU-core-based default.
Port constraints: Ports 80, 443, 12001–12004, 8080, and 8081 are reserved for proxying, control-plane, upstream, status, or readiness functions and cannot be used by proxied services.
Distribution: The maker links to the OpenNJet KIC user manual and source code from the release article.
Support: The maker lists developer and user mailing lists and a technical discussion QQ group (607280080).
Routing: It provides dynamic locations, host and path routing, load balancing, dynamic upstreams, canary releases, TLS termination and SNI.

Where it ranks on Freedom251

Best Kubernetes Ingress Controllers in 2026#18 of 27

Is OpenNJet Ingress Controller yours?

Claim it for free: prove the domain, then correct facts, plans and screenshots. An editor reviews every change.

Claim it free Promote OpenNJet Ingress Controller

Sources

njet.org.cn/cases/opennjet_kic-_v2.0/· checked 7 Oct 2026
gitee.com/njet-rd/open-njet-kic· checked 8 Oct 2026