Azure Kubernetes Service (AKS) vs. Google Kubernetes Engine

[Azure Kubernetes Service (AKS)] is great when you need to be able to deploy a large number of services in a highly repeatable way. Once you know how to use it, it is a very fast to stand up a new environment. However there is a lot you need to know to get to that point and it is a specialized area. This is not suitable for small teams who are supporting multiple product stacks.

Incentivized

Google Kubernetes Engine is well suited for dynamic and large workloads since it can scale up with usage. It is easily configurable, which allows for flexibility. User interface is simple to navigate, which reduces roadblocks for a team with people unfamiliar with Kubernetes. Great if you are already using other GCP services as it integrates well with that.

Incentivized

• To scale the microservices very easily.
• Easy to set up in CI/CD pipeline.
• It has a good pricing option as well in Azure. Basic works fine.
• Accelerates containerized application development for the developers.

Incentivized

• Deployment of a new GKE cluster is really fast in comparison to other cloud providers.
• GCP is ahead other vendors and always provide the most up to date Kubernetes version.
• GKE automation for master upgrade and the worker nodes pool works really well.

Incentivized

• GUI on azure portal need to enhanced.
• The feature set should be matching with Openshift which is also kubernetes based
• Troubleshooting errors

Incentivized

• Not as intuitive as it could be
• Documentation could be better, especially for people using other Google Cloud tools
• Not the preferred Kubernetes Engine for many apps

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

It's a great product if you learn it. It has flexibility and is very strong. Autoscaling and Resource management make running huge applications a breeze. Using Helm with Kubernetes and Terraform for infrastructure creation can totally automate your CICD pipeline. You also get easy access to CUDA cores for machine learning.

Incentivized

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

Incentivized

Google support is excellent and helpful, but the first answer is always so bureaucratic no matter how many logs, evidence, and information you sent.

Incentivized

Worked with very similar in-house-built Kubernetes/container management system. We are leveraging AKS as it's more robust and stable being in the technical space for quite some time. Also, it has got a vast number of management and security features which makes it more attractive. They even have a model where the cost can be reduced by up to 90% if the application can afford to handle a quick downtime once in a while.

Incentivized

We had to move several products to Google Cloud, and the Google Kubernetes Engine was the option recommended to us, so we investigated it and ran with it. Back then (2019), we were not aware of Cloud Run-provisioned K8s clusters, so our other option was a completely self-managed K8s cluster on Compute Engine VMs, which we did not have the knowledge of and capacity to handle.

Incentivized

• The ability to scale has reduced the need for headcount in IT
• The authentication process has kept us compliant with regulatory bodies
• The ability to replicate environments is great.

Incentivized

• Compared to other big K8s providers it has the best price/performance factors.
• Upgrade process from stable to regular versions
• Old stable releases: 1.15/1.16 should be in a stable branch.

Incentivized