Amazon Elastic Kubernetes Service (EKS) vs. Google Kubernetes Engine

Well suited for microservices architecture but can be a bit costly if less number of microservices or monolithic architecture hosted to be hosted on containers. Use of hybrid cluster instances also works well using both normal and fargate instances. Also the integration of audit and diagnostic logs of master nodes helps to reduce the unwanted access related issues.

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

• Upgrade the kubernetes clusters to the latest version with a single click
• Auto scaling policies to automatically scale the nodes
• Detailed logs and events on the cluster within the EKS clusters portal, cloudwatch logs and metrics

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

• AWSIAM integration with Kubernetes RBAC could be better.
• Enabling some add-ons like service mesh, and monitoring will be nice instead of having to install them yourself after the creation of the cluster.
• EKS bootstrap time could be faster ...

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

Cluster maintanence is reduced, easier to deploy resources, great observability insights

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

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

It feels like AWS is behind the EKS race, the only advantage I'm able to see right now is the support of IPv6, however, trying to promote AWS alternatives that are different from the market and more like a vendor locking solutions like ECS/Fargate have kept AWS behind and focusing on the wrong things. EKS needs to really improve its integration with the Kubernetes ecosystem and have an enterprise solution for monitoring, backups, and service mesh.

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

• Migrating all our workloads from ec2 VMs to containers running in Kubernetes has been a huge improvement for the management and resilience of our Infrastructure.
• EKS Upgrade process to a new version seems to be taking very long ....
• EKS creation time usually takes over 10 minutes in us-east-1, we would like faster creation times to be under 5 minutes.

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