OpenNJet Ingress Controller review
A self-hosted, open-source controller for teams that need flexible Kubernetes traffic routing.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
OpenNJet Ingress Controller is an open-source Kubernetes ingress controller based on the OpenNJet proxy. It processes standard Kubernetes Ingress resources for host- and path-based routing, alongside VirtualServer custom resources for advanced content-based routing. Teams can use it to direct cluster traffic, manage upstreams, terminate TLS, and handle HTTP as well as TCP, UDP, and WebSocket traffic. Its self-hosted deployment suits teams that want to operate routing infrastructure inside their Kubernetes environment rather than adopt a managed service.
Routing and traffic management are its clearest strengths. OpenNJet documents dynamic updates to routes and upstreams without reloading proxy configuration, round-robin and consistent-hash load balancing, upstream health checks, and cross-namespace configuration. Canary releases and traffic management provide ways to steer traffic during releases. TLS termination and SNI cover encrypted connections, while Prometheus metrics support monitoring workflows. The mix of Ingress API and VirtualServer resources gives teams a standard entry point plus a custom-resource option for more advanced routing rules.
The project is free and open source, with a self-hosted deployment model and community support. Its named integrations are ADC and Prometheus, so teams should assess how that footprint fits their existing platform rather than assume a broader supplied ecosystem. This is a practical fit for Kubernetes operators who value dynamic NGINX-style routing and can manage the controller themselves. Teams seeking a managed service, commercial support, or a controller whose fit depends on specific authentication or rate-limiting capabilities should compare alternatives against those requirements before choosing OpenNJet.
OpenNJet Ingress Controller pros and cons
- Where it wins
- Routes traffic with Kubernetes Ingress and VirtualServer resources
- Updates routes and upstreams dynamically without reloading proxy configuration
- Supports canaries, TLS/SNI, TCP/UDP, WebSockets and Prometheus metrics
- Where it doesn't
- Requires deployment within a Kubernetes environment
- Support is community-based
- Named integrations are limited to ADC and Prometheus
OpenNJet Ingress Controller fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update