Amazon Elastic Kubernetes Service (EKS) vs. Google Container Registry

It is well suited when you want to have a Kubernetes cluster in AWS Cloud and want to avoid all the management overhead of maintaining your own cluster in terms of the control plane. EKS seems to be lacking in features when compared with AKS and GKE. Backups, service mesh, and monitoring have a lot of room for improvements.

Incentivized

As a Cloud Engineer while working on a migration project we used GCR and my experience of using it is actually good the reason behind this is: 1: GCR uses industry-standard encryption to protect your data.2: GCR offers data loss prevention features to help you prevent sensitive data from being leaked or exposed and last but not the least is GCR provides audit logging so you can track who has accessed your data and when, because of these reasons its my go to tool.

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

• Object Immutability feature allows us to protect our code and backups from accidental or malicious changes.
• Data loss prevention feature helps us to prevent sensitive data from being leaked or exposed.
• GCR has support for machine learning which is in my opinion is best .

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

• The one area which i think GCR lacks is that it currently supports a limited number of file types
• The major flaw a felt while working on it is it does not have feature of object versioning and object locking

Incentivized

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

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

It is very easy to integrate GCR with other services and I integrated GCR with GKE and Cloud Build. 1: While working on one project I created one pipeline pulls the app's Docker image from GCR and builds the app's Docker image. Deployed that apps image in GKE. 2: Ive stored the data in GCR and that data was being used by cloud Run applications

Incentivized

• Good performance of platform without hiccups
• Less number of people required to manage cluster
• Easier to deploy new microservices

Incentivized

• As a DevOps Engineer , GCR has made a important contribution to my organisation because GCR can be used to store code and assets, which can help to reduce the development time for new projects.
• Using GCR has bee­n a cost-effective solution for us since­ we only pay for the storage we­ actually utilise. This has resulted in significant savings on our cloud storage­ expenses.
• We trust GCR be­cause they prioritise the­ security of our data by utilising industry-standard encryption. This assurance brings us pe­ace of mind, as we know our information is protecte­d.

Incentivized