Azure Kubernetes Service (AKS) vs. NGINX Ingress Controller

At one instance, there was a fire in our data center and the backup power had some issues because of which the whole DC went down. I believe with AKS and the replication it's easier to handle such a situation. Also, the scenario would have been pretty transparent to the end-users.

Incentivized

Best suited if we have to manage external traffic inside your Kubernetes cluster and want to use granular control to your applications.

Incentivized

• Scales quickly when the user base increases randomly
• Downgrades very fast if a bunch of users hop off the system
• Great dev UX for IT

Incentivized

• Provide access to containers
• Manage traffic
• Route traffic
• Lightweight
• Near to zero downtime

Incentivized

• Steep learning curve
• Expected charges are unclear until you see real production usage
• Operations teams need to learn an entirely new skill set

Incentivized

• Its not related to Ingress functionality but certificate management with cloud vendor would be a feature i would like to see.

Incentivized

Barring certain missing features such as operator management , open cluster management, it does gives lot of options to host containerized applications. The GUI may be improved and can give user more insights to the cluster rather than using command line tools. The integration with standard azure monitoring tools is a big plus to use Azure Kubernetes Service (AKS)

Incentivized

Microsoft support was really good, whenever we raise any ticket they come back to us within a couple of hours.

Incentivized

Due to cost efficiency. And using AZURE cloud for other services as well. Azure Kubernetes Service is more suitable to configure CI/CD pipelines. With a facility of automated or One click deployment and integration of the application. As compared with other Kubernetes Services like Amazon Elastic Kubernetes Service and Google Kubernetes Service, Azure Kubernetes is most cost-efficient with the same facilities and with an advantage to configure easily, manage easily, as it is one click manageable with Microsoft applications. It provides high Microsoft security to containers and secures applications from any kind of harm.

Incentivized

We are already using NGINX which is so reliable, it definitely lends weight to our decision to select NGINX Ingress Controller. Also, even though it is a little more complex to manage, NGINX Ingress Controller definitely have a richer feature set, better performance, caching, traffic management among other features which was why it was chosen.

Incentivized

• Positive impact in moving applications to cloud from the in-hose data center to save cost
• Sometimes got affected with some bugs on the AKS infrastructure but hasn't caused a big kios as our production footprint in AKS is not yet high

Incentivized

• Security is one of the best objective which we achieve with NGINX Ingress
• Cost optimization is one of the business objective

Incentivized