Azure Kubernetes Service (AKS) vs Kubernetes

• Highly repeatable process
• Minimizes the amount of software to install
• Easily scale resources to meet demand

Read full review

• Makes sure that the workload remains UP & running by maintaining the desired state.
• Gives a lot of flexibility in choosing the networking, storage, monitoring, etc solutions of your choice.
• The biggest advantage is to upgrade the application with a new version without any downtime.
• Portability of the code is possible up to a great extent.

Read full review

• Need to update cluster manually
• Policies cannot be updated for existing components
• if any change in policy every has to create cluster

Read full review

• We had several problems with its NFS, which is responsible for syncing the code across the cluster
• On several instances the pods go into UNKNOWN state in which case restarting the entire node is the only solution
• As a user of the existing setup given to me, I wasn't able to allocate only some CPU cores on a single host. It was either all or zero making cluster utilization sub-optimal

Read full review

• 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

Read full review

• Because of microservices, Kubernetes makes it easy to find the cost of each application easily.
• Like every new technology, initially, it took more resources to educate ourselves but over a period of time, I believe it's going to be worth it.

Read full review