Kubernetes vs NGINX Ingress Controller comparison

"Kubernetes' most valuable features include scalability and deployment."

"The solution has many valuable features but the most impressive is the ability to scale an application and continuously monitor if all the components of the application are functioning correctly."

"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 best thing about Kubernetes is orchestration. It is very good. We will not see much downtime unless there are some human errors. We do not see much downtime or issues with the container or automation."

"The most valuable feature of the platform is the ability to load some of the containers that were previously managed by humans."

"Kubernetes' most valuable features are scaling, deployment, and container management."

"I like the replication center and the configuration."

"I like that it gives you all the flexibility, for example, auto-scaling. Everything is figured out exactly right. It manages all your workloads without much intervention. It can scale in, scale out, and with security. Everything looks pretty good compared to the old legacy way of working."

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

"We would to have additional features related to security within the API, instead of needing to install add-ons."

"We would like to see more validation tools added to this solution, this would provide pre-deployment analysis that developers could use before publishing their infrastructure."

"Some Kubernetes technical support would be helpful."

"This product should have a more advanced built-in scheduler that uses real application metrics in the scheduling strategy."

"The management needs to be improved."

"I'm expecting more improvement on the UI development side, which can be reflected in each object that is part of Kubernetes, like the Pod, deployment set, ReplicaSet, ConfigMap, Secrets, and PersistentVolume."

"I think that the GUI dashboard in Kubernetes is very simple and that there are no great options."

"The initial setup of Kubernetes is difficult. However, if you are used to the flow then it is easier. The length of time it takes for the implementation depends on the project."

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

"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 open source. But we have to manage Kubernetes as a team, and the overhead is a bit high. Compared with the platforms like Cloud Foundry, which has a much less operational overhead. Kubernetes, I have to manage the code, and I have to hire the developers. If someone has a product, a developer should know exactly what he's writing or high availability, and all those things may differ the costs."

"Kubernetes is free; it's open-source software."

"Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it"

"I am using the solution's open-source version."

"The solution is open source and has no fees."

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