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

HPE Ezmeral Container Platform vs NGINX Ingress Controller comparison

 

Comparison Buyer's Guide

Executive Summary

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

HPE Ezmeral Container Platform
Ranking in Container Management
19th
Average Rating
7.0
Reviews Sentiment
7.7
Number of Reviews
2
Ranking in other categories
No ranking in other categories
NGINX Ingress Controller
Ranking in Container Management
8th
Average Rating
8.4
Reviews Sentiment
6.0
Number of Reviews
19
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Container Management category, the mindshare of HPE Ezmeral Container Platform is 2.5%, up from 1.3% compared to the previous year. The mindshare of NGINX Ingress Controller is 1.7%, up from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management Mindshare Distribution
ProductMindshare (%)
NGINX Ingress Controller1.7%
HPE Ezmeral Container Platform2.5%
Other95.8%
Container Management
 

Featured Reviews

CC
Pre-Sale at Yip Intsoi
Effective cost management achieved with robust storage features but user experience and data management require improvements
HPE Ezmeral Container Platform is not user-friendly and has many parts that are more difficult than Cloudera. It is also a complex solution and has low features for data management. For example, it cannot make a data catalog or process data lineage without third-party support, which increases the cost for development.
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.

Quotes from Members

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

Pros

"If customers focus on primary apps or if they are using them for data science, this is a good solution."
"The stability of the HPE Ezmeral Container Platform is good, and I rate it an eight out of ten."
"From my experience, I think the main benefit NGINX Ingress Controller provides to the end user is the reliability of NGINX Ingress Controller itself."
"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."
"NGINX Ingress Controller is a truly good tool that has proven its capability in the market."
"We are using NGINX Ingress Controller for the past three to four years, and it is very reliable for us and it can handle the traffic based on our load as well."
"The overall time and manual work have been reduced since we started using NGINX Ingress Controller."
"This shift away from manual config management has made my team's productivity and efficiency much easier."
"In many ways, NGINX Ingress Controller has provided cost reduction by eliminating our per-service load balancers."
"NGINX Ingress Controller has positively impacted my organization by achieving cost reduction since we have just one load balancer instead of one per service, which cuts down our cloud spending."
 

Cons

"If a customer is focused on process automation or API usage, I would not recommend this solution, but it is good to use for Data Science."
"HPE Ezmeral Container Platform is not user-friendly and has many parts that are more difficult than Cloudera. It is also a complex solution and has low features for data management."
"The modernization in Ezmeral could be improved."
"NGINX Ingress Controller itself is a great product, but when considering a complete solution, there are limitations."
"However, there is still a major limitation in GUI capability to manage and observe."
"When it comes to how NGINX Ingress Controller can be improved, I think we can add documentation as one of the points."
"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."
"Nowadays, the quality has been degrading, and I do not expect the same level of service."
"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."
"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."
"The core dynamics and core features for databases involve the paywall; the paywall is what concerns me."
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Computer Software Company
11%
Manufacturing Company
11%
Comms Service Provider
8%
Outsourcing Company
20%
Computer Software Company
13%
Manufacturing Company
9%
Financial Services Firm
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise3
Large Enterprise9
 

Questions from the Community

What needs improvement with HPE Ezmeral Container Platform?
HPE Ezmeral Container Platform is not user-friendly and has many parts that are more difficult than Cloudera. It is also a complex solution and has low features for data management. For example, it...
What is your primary use case for HPE Ezmeral Container Platform?
We want to replace the existing Cloudera data lake with HPE Ezmeral Container Platform ( /products/hpe-ezmeral-container-platform-reviews ).
What advice do you have for others considering HPE Ezmeral Container Platform?
I rate the HPE Ezmeral Container Platform seven out of ten because it has strong features for storage but lacks certain data management functionalities, requiring additional investments for third-p...
What is your experience regarding pricing and costs for NGINX Ingress Controller?
Regarding the pricing of NGINX Ingress Controller, I think till now it was free. Nowadays, I think since last March, they have started charging. Till March 2026, I think it was free. Then later on,...
What needs improvement with NGINX Ingress Controller?
A negative point about NGINX Ingress Controller is configurational control over the traffic distribution. When the request comes in, it has given a bit light control over the configuration of how i...
What is your primary use case for NGINX Ingress Controller?
I use NGINX Ingress Controller mainly for routing purposes inside the cluster. I connected our ALBs and NLBs with NGINX Ingress Controller. From that point onward, I used it for path-based routing....
 

Overview

 

Sample Customers

data iku, StreamSets, unravel
Information Not Available
Find out what your peers are saying about HPE Ezmeral Container Platform vs. NGINX Ingress Controller and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.