No more typing reviews! Try our Samantha, our new voice AI agent.

NGINX Ingress Controller vs Nutanix Kubernetes Engine NKE [EOL] comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 1, 2025

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

NGINX Ingress Controller
Average Rating
8.6
Reviews Sentiment
6.2
Number of Reviews
17
Ranking in other categories
Container Management (9th)
Nutanix Kubernetes Engine N...
Average Rating
7.6
Reviews Sentiment
6.9
Number of Reviews
14
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Suleiman  Mohammed - PeerSpot reviewer
Senior Database Engineer, SRE at Interswitch Group
Routing for long-lived data connections has improved but protocol-aware checks still need work
NGINX Ingress Controller can be improved, and my team's concern would be database protocol-aware health checks for Transport Server since that is what NGINX is more focused on. Right now, even on Plus, a Transport Server health check is essentially a TCP connect or maybe a basic send-expect. For a database, that is a weak signal. The listener being up tells you almost nothing about whether Postgres is actually serving, whether a replica is lagging, or whether it is in recovery. I would love a way to define a health check that does something protocol-aware, even something as simple as you open a connection, run a SELECT one, which is the most popular test, and expect a row for Postgres or a PING for Redis. Without that, I am relying on the database's own infrastructure to pull bad replicas, and the ingress will happily continue routing to a replica that answers TCP but is serving stale reads. Better idle connection management for long-lived stream connections can also be improved. A pooled database connection sitting idle between transactions is healthy in my opinion, but the proxy's instinct is to reap idle connections. You can crank timeouts way up, but that is a blunt instrument. I would like to add that specifically for databases, the need for improvement becomes clearer. Every client connection through NGINX becomes a backend connection, one-to-one. A client connection through NGINX and a client connection through a connection pooler are sitting because they are going to get sent to the backend connection. It does not multiplex; it does not understand transaction boundaries. It cannot reuse a connection across clients. If you put it in front of Postgres without a real pooler behind it, you have just built a very efficient way to exhaust the max connection. The architecture is always client, ingress, connection pooler which is either pgBouncer or ProxySQL, then the actual engine which is Postgres or MySQL. Never let it be clients straight to the database. NGINX Ingress Controller's mode is one client connection to one backend connection with no multiplexing and no protocol awareness, which would be an issue for you.
reviewer2741271 - PeerSpot reviewer
Nutanix Administrator at a consultancy with 10,001+ employees
Has provided seamless upgrade experiences and robust technical support
I have heard there are many features added in NKP that are not available in Nutanix Kubernetes Engine NKE, such as load balancer features. The unified control plane feature is not being used in Nutanix Kubernetes Engine NKE. We are currently using a third-party tool for load balancing, but going forward, NKP will include load balancer, ingress, and egress features, making infrastructure management much easier. There is no auto-scaling feature in Nutanix Kubernetes Engine NKE; however, NKP offers it. In NKE, we created additional worker nodes and increased CPU and RAM capacity, but it required manual intervention. Concerning policy-driven governance in Nutanix Kubernetes Engine NKE, we have the ability to implement RBAC at the cluster level, which helps maintain security by not granting full admin privileges to every end user, thus restricting access effectively.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"NGINX Ingress Controller has positively impacted my organization by helping us with exposing our applications and managing security and auto-scaling."
"The main benefit is that it is better in performance, provides security with App Protect and WAF and DDoS, and delivers high performance and high stability."
"NGINX Ingress Controller has positively impacted my organization by allowing us to handle many requests from different applications and customers, serving as the frontier of all our backend applications."
"NGINX Ingress Controller is a truly good tool that has proven its capability in the market."
"This shift away from manual config management has made my team's productivity and efficiency much easier."
"NGINX Ingress Controller has positively impacted the organizations where I have worked by providing a very easy and cost-free way to add layer 8 security to their infrastructure."
"NGINX Ingress Controller has positively impacted my organization in that all my ingress resources, services, and internal and external communications between different services are quite smooth, and we can control our service exposure and service access easily using NGINX Ingress Controller, which makes my organization really happy."
"The best features that NGINX Ingress Controller offers in my experience are that the ingress controller can perform content-based routing and SSL termination, which is usually not available on software-only solutions and typically comes with hardware-based solutions."
"We can add some add-ons and plugins to the product if we need to."
"Karbon is embedded in the hypervisor, there are no deployment costs and the administration is via Prism Central."
"The most valuable features of the Nutanix Kubernetes Engine (NKE) are its simplicity and efficiency during the initial cluster creation phase."
"Nutanix's support is really good."
"The technical support is excellent."
"Nutanix is very stable and reliable, based on my experience with many customers, including large banks and telcos."
"We can do a lot of provisioning."
"The solution provides no downtime features. If we face issues, we create a new port, deploy it there, and then drop the existing one. This way, we avoid NKE downtime on our website."
 

Cons

"NGINX Ingress Controller can be improved with better documentation."
"NGINX Ingress Controller itself is a great product, but when considering a complete solution, there are limitations."
"Overall NGINX Ingress Controller is a good tool to use, but the main drawback is the annotation part, as managing many paths and features can get quite tedious and complicated."
"Most customers are satisfied with the reverse proxy capability, but the main issue is that the Ingress NGINX, the one that is most widely used, will be deprecated this month."
"I think NGINX Ingress Controller can be improved by not being deprecated."
"However, there is still a major limitation in GUI capability to manage and observe."
"NGINX Ingress Controller can be improved by implementing faster deployment of new services, simplifying SSL or TLS management, and enhancing faster troubleshooting by providing more logs."
"Nowadays, the quality has been degrading, and I do not expect the same level of service."
"I would like to have more nodes for availability and storage."
"There have been cases where we've deployed with Karbon and haven't seen that it includes errors."
"There is no auto-scaling feature in Nutanix Kubernetes Engine NKE; however, NKP offers it. In NKE, we created additional worker nodes and increased CPU and RAM capacity, but it required manual intervention."
"It's mostly for lab purposes; we haven't seen a lot of traction in the market from enterprise customers yet."
"Areas for improvement in Nutanix Kubernetes Engine (NKE) include upgrading management capabilities and enhancing the user interface for improved usability."
"The product lacks some virtualization capabilities, making it an area for improvement where the solution can focus on providing users with more virtualization capabilities related to disk systems."
"Nutanix has limitations compared to VMware, particularly in testing and industry tie-ups with different OEMs. Deploying virtual machines, especially for industrial automation, can be challenging due to compatibility issues."
"In the next release, I would like to have automatic dynamic scaling, both upscaling and downscaling."
 

Pricing and Cost Advice

Information not available
"I rate NKE's pricing a six out of ten."
"While deploying Kubernetes clusters on Nutanix is cost-effective, there may be additional costs for remote branch offices where Kubernetes is less common."
"The product's licenses are included in the software version deployed in our data center."
"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."
"The platform is averagely priced. I rate the pricing as four out of ten."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
900,747 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
14%
Computer Software Company
13%
Manufacturing Company
10%
Financial Services Firm
9%
Manufacturing Company
12%
Computer Software Company
11%
Government
11%
Financial Services Firm
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise3
Large Enterprise8
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise2
Large Enterprise4
 

Questions from the Community

What is your experience regarding pricing and costs for NGINX Ingress Controller?
The pricing for NGINX Ingress Controller is overall acceptable, and I would not say it is great. The setup cost was also acceptable, and the licensing was straightforward.
What needs improvement with NGINX Ingress Controller?
The annotation part of NGINX Ingress Controller is good, but it can be tedious when there are many features to specify in the annotation section, which sometimes gets messy and could be improved. H...
What is your primary use case for NGINX Ingress Controller?
NGINX Ingress Controller is primarily used for routing in my team's Kubernetes cluster where we run multiple microservices. We deployed NGINX Ingress Controller on a cluster with around 20 microser...
What needs improvement with Nutanix Kubernetes Engine NKE?
In terms of features, I cannot comment technically, but the real value is the consolidated out-of-the-box solution that Nutanix offers. Nutanix has built great branding and a lot of credibility and...
What is your primary use case for Nutanix Kubernetes Engine NKE?
I have experience with OpenShift, Kubernetes, and Nutanix, as we are one of the largest Nutanix resellers in the Middle East. We handle Kubernetes on the cloud as well, so we manage most of the Kub...
What advice do you have for others considering Nutanix Kubernetes Engine NKE?
I don't have a technical role, but we are a system integrator, so we sell solutions such as OpenShift and Kubernetes as part of the sales team. We are a reseller called eSky IT, and I serve as the ...
 

Also Known As

No data available
Nutanix Karbon
 

Overview

 

Sample Customers

Information Not Available
JetBlue, International Speedway Corporation, SAIC Volkswagen
Find out what your peers are saying about Red Hat, Amazon Web Services (AWS), Kubernetes and others in Container Management. Updated: June 2026.
900,747 professionals have used our research since 2012.