"Azure is the best at Kubernetes. There are great tools in [other clouds] However, if speed to deploy and respond to user traffic is the most significant decision, then AKS is the winner (specifically with k8s)."
Conversation
Replying to
The helm charts used to determine deployment speeds are way out of date on storage classes and service annotations both of which would easily beat out what I’m seeing from AKS. Happy to test live and proves this article is unbelievably flawed.
4
11
I suggest testing reliability in the future. How does it take for a pod w/ attached PD to failover to another node for example. Another good metric. How many times has the cloud provider left gapping security holes in agents or taken down all Linux nodes when updating drivers.
1
4
Show replies
Microsoft is good at many, many things, including Kubernetes. And marketing.
But the most important web properties choose GKE because it's objectively the best way to provision, scale, secure, configure, and operate high-performing Kubernetes clusters.
1
1
14
Show replies
Replying to
Couldn’t agree more, even after working with GKE for a long time, there’s no denial that AKS is superior and easier to start. It’s just amazes me how all cloud consoles are terrible 😂
2
Replying to
Replying to
Based on my experience, GKE followed by AKS, then in complete last place EKS
4
Replying to
Interesting take. During my time at CoreOS when porting Tectonic, we literally found that Azure LBs didn’t have their MTUs configured properly and were thus dropping packets. This was soon after fixed by the Azure guys but that definitely didn’t inspire much confidence..
5