Kubernetes vs NGINX Ingress Controller comparison

"There's a lot of community support if you need to get help."

"Once you get it configured properly, it's a stable solution."

"We use this solution for the hosting of micro-services. Kubernetes helps us to orchestrate all the containers hosting these micro-services."

"Provision of a managed platform as a service."

"The scalability seems quite good."

"The best thing about Kubernetes is that most of the containerized applications are centralized."

"There are features that come out of the box with Kubernetes, with respect to scaling, reliability, etc. It's the leading container management platform. There are other competing ones, but this is the leading one. It has multiple instances of the application running. If one of them goes down, the other one automatically spins up."

"It's really scalable and efficient for resource management."

"NGINX Ingress Controller has positively impacted our organization by saving us a lot of time, reducing our downtime, and allowing for safe releases."

"The solution has some issues regarding availability during high loads. Worker nodes are sometimes unavailable, affecting the overall availability of the applications. This is a bug or underlying problem with the tool, and Azure and other providers are looking into improving this by releasing new versions of Kubernetes that fix some of the platform's issues."

"The price is something they need to improve."

"The management needs to be improved."

"There are features in Google Cloud or AWS that aren't in Azure. They need to implement a couple more tools in Azure."

"There are several areas where Kubernetes could improve."

"In the financial service sector, I'd rate scalability an eight out of ten. But do it in a controlled manner, not auto-scaling. If your application has a bug and you enable the autoscaler, it will spike your costs. If someone deploys an application with a bug, that's automatically a problem."

"One thing I noticed is when you have multiple deployments and your node count increases beyond eight or nine, the container creation process doesn't copy properties correctly."

"I would rate the stability as five out of ten. If any containers take more space, sometimes the cluster goes down."

"One improvement I see for NGINX Ingress Controller is that the obvious downside is the cost, as you pay for the license on top of AWS infrastructure and the pricing is not cheap."

"The solution itself is open-source, so there is no cost attached to it. However, it requires a virtual machine to operate, which does come at a cost; a choice of a pay as you go model, or a monthly charge via an enterprise agreement. There is a pricing calculator available, where organizations can determine the level and number of virtual machines required, and how much that will cost."

"I would say the solution is worth the money, but it depends on the required workloads, the type of workload, and the scaling requirements etc."

"Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services."

"The price of Kubernetes could be lower. However, it is less expensive than VMware Tanzu. Additionally, technical support is expensive. The overall cost of the solution is approximately $1,000 annually."

"Kubernetes is open-source. Kubernetes is free, but we're charged for AWS utilization."

"If you're using a public cloud, the cost depends on the number of nodes you are planning to deploy Kubernetes on."

"There is a license to use Kubernetes."

"The solution is affordable."