When selecting a managed Kubernetes service like AKS, EKS or GKE, it’s good to know the strengths and weaknesses of each. All of these services have solved how to easily deploy Kubernetes, but are different for how you configure clusters correctly or effectively leverage the service. By understanding these strengths and weaknesses, you can select a service right for your application and also save time having to learn multiple services and each of its specific nuances.
As a disclaimer, if I’m asked what to use, I’d counter by asking what your application is doing and what services it depends on. Kubernetes isn’t the only thing your application needs so you’ll need to factor in requirements - security, additional cloud services, and node customization for example. Without digging into that for this blog, here is a high level summary. If you do want to discuss your specific application, feel free to get in touch.
TL;DR: AKS is ideal if you're a Windows or .NET shop or already using Azure; EKS is good if you require a high level of customization; GKE is easy to get started and use.
In alphabetical order, here is a quick summary of AKS, EKS and GKE. It is not an exhaustive list and could be debated as some strengths or weaknesses you might view as a strength for your individual application.
Leveraging a managed Kubernetes service is not the same as using Kubernetes effectively. Fairwinds helps companies using AKS, EKS or GKE configure clusters correctly and effectively leverage the service.
Get Kubernetes security, cost allocation and avoidance, compliance and guardrails in one platform for free with Fairwinds Insights.
Learn more about what Fairwinds adds to AKS, EKS or GKE.