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

F5 and Nutanix are both solutions in the Container Management category. Additionally, 100% of F5 users are willing to recommend the solution, compared to 100% of Nutanix users who would recommend it.

NGINX Ingress Controller

Read 17 NGINX Ingress Controller reviews

1,226 Views
1,226 Comparison Views

100% willing to recommend

Nutanix Kubernetes Engine N...

Read 14 Nutanix Kubernetes Engine NKE [EOL] reviews

100% willing to recommend

NGINX Ingress Controller

Nutanix Kubernetes Engine N...

Comparison Buyer's Guide

Download the report

Executive SummaryUpdated on Sep 1, 2025

Nutanix Kubernetes Engine NKE [EOL] and NGINX Ingress Controller are competing solutions in the Kubernetes ecosystem. NGINX Ingress Controller is often seen as superior due to its robust features which users see as justifying the cost.

Features: Nutanix Kubernetes Engine NKE offers seamless Kubernetes infrastructure management, automated scaling, and enhanced security. NGINX Ingress Controller provides advanced load balancing, traffic routing, and SSL termination.

Ease of Deployment and Customer Service:Nutanix Kubernetes Engine NKE is recognized for its simpler deployment within Nutanix environments and reliable support. NGINX Ingress Controller offers extensive online resources and community support facilitating easier troubleshooting.

Pricing and ROI: Nutanix Kubernetes Engine NKE's setup costs are often seen as competitive offering a sensible return on investment by reducing operational complexities. NGINX Ingress Controller, although potentially higher in initial cost, is valued for its high return through traffic optimization and reliability, leading to better long-term gains.

To learn more, read our detailed Container Management Report (Updated: June 2026).

Buyer's Guide

Container Management

June 2026

Download the complete report

Helped 900,747 peers since 2012

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

Ranking in other categories

Container Management (9th)

Nutanix Kubernetes Engine N...

Average Rating

7.6

Reviews Sentiment

6.9

Number of Reviews

Ranking in other categories

No ranking in other categories

Featured Reviews

Suleiman Mohammed

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.

Read full review

reviewer2741271

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.

Read full review

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 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 my organization since I have been using it in production for over three to four years."

"NGINX Ingress Controller has positively impacted my organization by definitely improving my team's efficiency in terms of multiple load balancers and complex routing rules we can configure there, resulting in a single, easy-to-manage layer."

"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."

"In many ways, NGINX Ingress Controller has provided cost reduction by eliminating our per-service load balancers."

"However, the response, throughput, and solid performance we receive after implementation are often worth it."

"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."

More NGINX Ingress Controller pros

"We can add some add-ons and plugins to the product if we need to."

"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."

"Scalability-wise, I rate the solution a ten out of ten."

"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."

"The technical support is excellent."

"The solution is easy to manage. You can get everything in a single platform. It is also easy to work with Terraform as a code."

"Karbon is embedded in the hypervisor, there are no deployment costs and the administration is via Prism Central."

More Nutanix Kubernetes Engine NKE [EOL] pros

Cons

"NGINX Ingress Controller can be improved with better documentation."

"The core dynamics and core features for databases involve the paywall; the paywall is what concerns me."

"In my use case with NGINX Ingress Controller, when we have multiple services, it becomes messy and overburdened to add the annotations to define the policy and the annotations of each service, making it a bit complex."

"I think NGINX Ingress Controller could be improved by adding many features and functions regarding firewalls, similar to what a professional API gateway offers, so those functionalities can be integrated with NGINX Ingress Controller."

"I think NGINX Ingress Controller can be improved by not being deprecated."

"The main feature I want to see included is the ability to reduce namespace specifications."

"Nowadays, the quality has been degrading, and I do not expect the same level of service."

"When it comes to how NGINX Ingress Controller can be improved, I think we can add documentation as one of the points."

More NGINX Ingress Controller cons

"We need a backup of production clusters."

"In the next release, I would like to have automatic dynamic scaling, both upscaling and downscaling."

"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."

"Areas for improvement in Nutanix Kubernetes Engine (NKE) include upgrading management capabilities and enhancing the user interface for improved usability."

"NKE could benefit from additional features that support more advanced Kubernetes functionalities and configurations."

"GUI lacks sufficient information to help with understanding the installation and process."

"One major issue we faced was that appliances couldn't migrate from VMware to the tool. However, this seems to be a common problem across platforms. We've seen the same issue when migrating from VMware to RHV or other solutions. It's not specifically a Nutanix problem but rather an issue migrating appliances from one VM infrastructure to another. Some kernel-level and storage-level issues impact this process."

"There have been cases where we've deployed with Karbon and haven't seen that it includes errors."

More Nutanix Kubernetes Engine NKE [EOL] cons

Pricing and Cost Advice

Information not available

"The platform is averagely priced. I rate the pricing as four out of ten."

"I rate the product price a five on a scale of one to ten, where one is cheap, and ten is expensive."

"I rate NKE's pricing a six out of ten."

"The product's licenses are included in the software version deployed in our data center."

"While deploying Kubernetes clusters on Nutanix is cost-effective, there may be additional costs for remote branch offices where Kubernetes is less common."

See which vendors are best for you

Use our free recommendation engine to learn which Container Management solutions are best for your needs.

See recommendations

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

Manufacturing Company

12%

Computer Software Company

11%

Government

11%

Financial Services Firm

Company Size

By reviewers

Large Enterprise

Midsize Enterprise

Small Business

By reviewers
Company Size	Count
Small Business	8
Midsize Enterprise	3
Large Enterprise	8

By reviewers
Company Size	Count
Small Business	10
Midsize Enterprise	2
Large Enterprise	4

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.

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

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...

See all answers

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 ...

See all answers

Comparisons

Kubernetes vs NGINX Ingress Controller

Compared 35% of the time

Docker vs NGINX Ingress Controller

Compared 22% of the time

Red Hat OpenShift Container Platform vs NGINX Ingress Controller

Compared 14% of the time

VMware Tanzu Platform vs NGINX Ingress Controller

Compared 10% of the time

Nutanix Kubernetes Platform (NKP) vs NGINX Ingress Controller

Compared 9% of the time

More NGINX Ingress Controller Competitors

Nutanix Kubernetes Platform (NKP) vs Nutanix Kubernetes Engine NKE [EOL]

Compared 12% of the time

VMware Tanzu Platform vs Nutanix Kubernetes Engine NKE [EOL]

Compared 11% of the time

Docker vs Nutanix Kubernetes Engine NKE [EOL]

Compared 7% of the time

Kubernetes vs Nutanix Kubernetes Engine NKE [EOL]

Compared 7% of the time

HPE Ezmeral Container Platform vs Nutanix Kubernetes Engine NKE [EOL]

Compared 4% of the time

More Nutanix Kubernetes Engine NKE [EOL] Competitors

Product Reports

Buyer's Guide

NGINX Ingress Controller

June 2026

Download NGINX Ingress Controller product report

Buyer's Guide

Nutanix Kubernetes Engine NKE [EOL]

June 2026

Nutanix Kubernetes Engine NKE [EOL] report

Download Nutanix Kubernetes Engine NKE [EOL] product report

Also Known As

No data available

Nutanix Karbon

Overview

NGINX Ingress Controller efficiently manages external access to services in Kubernetes, ensuring secure connection handling and traffic flow. Its robust architecture supports high availability, scalability, and performance, making it a vital component for managing ingress resources.

NGINX Ingress Controller serves as a critical ingress point for Kubernetes clusters, offering vast customization options and seamless integration with NGINX and NGINX Plus. It provides enterprises with scalable solutions for enforcing policies and maintaining control over traffic routing. The controller supports various load balancing algorithms and TLS termination, making it a versatile tool for organizations aiming to optimize their containerized environments.

What are the most important features of NGINX Ingress Controller?

High Performance: Delivers efficient load balancing and reverse proxying, ensuring fast response times.
Security: Offers advanced configuration for secure access, including TLS/SSL termination and authentication.
Extensibility: Facilitates custom configurations through a flexible annotation system.
Scalability: Supports scalable infrastructure with efficient handling of traffic spikes.

What benefits or ROI should users look for in reviews?

Improved Resource Management: Optimizes the use of cluster resources, leading to reduced operational costs.
Enhanced User Experience: Low latency and high uptime contribute to better service quality.
Operational Efficiency: Streamlines deployment processes, increasing team productivity.
Security Assurance: Robust security features protect sensitive data.

In the finance sector, NGINX Ingress Controller helps manage the heavy transactional load while ensuring data privacy and compliance. E-commerce platforms benefit from its superior performance during traffic surges, enhancing customer satisfaction. In the tech industry, it integrates easily with microservices architectures, simplifying operations and reducing downtime.

Nutanix Kubernetes Engine NKE [EOL] offers easy deployment, efficient resource management, and seamless integration with existing infrastructure, supporting virtualization and configurable RBAC.

Nutanix Kubernetes Engine NKE [EOL] simplifies Kubernetes cluster deployment and management, offering robust features such as health checks and seamless upgrades. It integrates with existing systems, supports virtualization, and provides a unified console. Automatic load management and scalability contribute to its stability. Though migrating via VMware poses challenges and documentation updates are needed, potential enhancements include dynamic resource scaling, advanced backup options, and improved disaster recovery. NKE is ideal for microservices, container management, and application modernization, playing a vital role in DevOps settings.

What are the key features of Nutanix Kubernetes Engine NKE [EOL]?

Easy Deployment: Simplifies cluster setup and management for quick ramp-up.
Resource Allocation: Efficiently allocates computing resources for optimized operations.
Seamless Upgrades: Handles updates without causing downtime.
Integration: Works with existing infrastructure, allowing virtualization support.
Console Management: Offers a single interface for robust management features.

What benefits should users look for in Nutanix Kubernetes Engine NKE [EOL]?

Cost-Effectiveness: Provides a reliable Kubernetes platform with reduced operational costs.
Scalability: Ensures stability and growth alongside increasing demands.
Support Features: Includes robust technical support for a seamless experience.
Efficiency: Enhances workload management in DevOps environments.
Configurable Options: Allows tailored RBAC and scalable virtualization benefits.

Nutanix Kubernetes Engine NKE [EOL] is deployed in industries focusing on microservices and application modernization, serving development to testing environments. It integrates with hardware and API tools, supporting DevOps workloads and infrastructure management. Primarily used on-premises, it supports large-scale application deployment leveraging network capabilities.

Nutanix

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.

DOWNLOAD NOW

900,747 professionals have used our research since 2012.

See our list of best Container Management vendors.

We monitor all Container Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.