Kubernetes vs NGINX Ingress Controller comparison

"The easy management of containers is one of the main features I have found useful."

"I like that it has really boosted cloud-native development and stood the test of time. The underlying architecture allows one to scale as per the business KPIs much faster."

"Auto-scaling and self-healing features are very good."

"The cloud-managed Kubernetes allow us to take care of a big system and deployment and container management without having a big operational team."

"The most valuable feature of Kubernetes is the integration with other solutions, such as Formative and Grafana."

"The most valuable feature is that it's a container orchestrator. It has a huge user base and it is easily incorporated into all of the public clouds."

"The Desired State Configuration is a handy feature; we can deploy a certain number of pods, and the tool will ensure that the state is maintained in our desired configuration."

"The most valuable feature is the Zero Touch Operations, which involves a new way of performing operations and support. We do not have to do maintenance, the operations are very simple."

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

"One area where Kubernetes could improve is troubleshooting. The current process for troubleshooting and installation can be challenging, especially with a large ecosystem. Better tools and artificial intelligence capabilities developed to assist with troubleshooting, configuration, and support would be helpful. This improvement would be particularly beneficial for large enterprise customers."

"Lacks some scalability and more user-friendly operability."

"The security of the solution is in its infancy and needs a lot of work."

"The user-interface in regards to the other solution can be improved."

"The price is something they need to improve."

"The setup and operation of the product should be simplified."

"We faced a challenge while migrating and upgrading versions of Kubernetes."

"Some Kubernetes technical support would be helpful."

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

"If you have a solid AKS and a solid DevOps process, you'll automatically get an ROI, not just in terms of cost but also in how quickly you can see your business application progress."

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

"In addition to Kubernetes, you have to pay for support."

"This is an open-source solution, so there are no licensing costs associated with its use."

"We use the solution's open-source version."

"The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything."

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

"There is a license to use Kubernetes."