4 ms·

I realize that Azure isn't as popular in the US startup crowd (and certainly not on HN), but you really cannot mention EKS without also mentioning AKS which is

by verst 8y ago

I realize that Azure isn't as popular in the US startup crowd (and certainly not on HN), but you really cannot mention EKS without also mentioning AKS which is much more mature IMHO. And ACI (Azure Container Instances) is a serverless container offering that was launched before Fargate. Beyond the Azure offering, Microsoft has also shown tremendous commitment to the Kubernetes ecosystem at large. Take a look at the many Kubernetes open source tools created by Microsoft that work with Kubernetes anywhere (!!!): [1] Helm (initially created by Deis, acquired by Microsoft) [2] Virtual Kubelet [3] Draft [4] Brigade [5] VSCode: Kubernetes Tools And more... [1]: helm.sh [2]: https://github.com/virtual-kubelet/virtual-kubelet [3]: https://github.com/azure/draft [4]: https://github.com/azure/brigade [5]: https://github.com/Azure/vscode-kubernetes-tools Disclaimer: I'm a developer advocate for Kubernetes / Linux at Azure (but a member of the community first and foremost). I've never run a Windows Container, and I don't have a single Windows VM in Azure ;) I encourage you to take a close look at the Azure offering. It's actually very awesome!

zaat 8y ago
>without also mentioning AKS which is much more mature IMHO. AKS is anything but mature.It's barely working. Last month I was at Microsoft event and everyone was suppose to launch an environment. By the fifth or six environment, provisioning died and no one could provision an environment. And I mean it died globally, regardless of the region you tried to run it at. Provision time is awful even when no one is "stress testing" the provisioning engine. This is all good and acceptable, relatively, when the service state is labeled as preview, which is how it is labeled officially. Mature isn't a word to use in regards to AKS currently. The hype Microsoft advocates try to build around AKS gives the impression a highly puffed CV of a junior dev, and IMHO it is unfortunate and a wrong way to build trust. It is fine that Azure haven't yet developed state of the art kubernetes cloud service, no one except Google have, just don't claim you did if you want us to believe you when it labeled GA that we can use it for real workloads.
- verst 8y ago
  You are correct. The provisioning sucked. I will be fully transparent about that. In fact, I had the same problems myself. You can see the list of issues here [1]. That provisioning madness is actually unrelated to AKS, but it's being addressed by the team. This is one of the reasons why the service isn't GA yet. I'd say give it a try in the EastUS region, or some time after GA. Once you do have an AKS cluster up it all works well. [1]: https://github.com/Azure/AKS/issues https://github.com/Azure/AKS/issues
bboreham 8y ago
I’m sure it is immensely irritating to Google that they aren’t even second to AWS, but I’m pretty sure it was not Microsoft they were aiming at with Kubernetes. To me, it’s a re-run of the X Window System playbook, where Digital managed to break Sun and Apollo’s lock on workstation tools. Digital didn’t particularly win that one either.

by verst 8y ago

zaat 8y ago

>without also mentioning AKS which is much more mature IMHO. AKS is anything but mature.It's barely working. Last month I was at Microsoft event and everyone was suppose to launch an environment. By the fifth or six environment, provisioning died and no one could provision an environment. And I mean it died globally, regardless of the region you tried to run it at. Provision time is awful even when no one is "stress testing" the provisioning engine. This is all good and acceptable, relatively, when the service state is labeled as preview, which is how it is labeled officially. Mature isn't a word to use in regards to AKS currently. The hype Microsoft advocates try to build around AKS gives the impression a highly puffed CV of a junior dev, and IMHO it is unfortunate and a wrong way to build trust. It is fine that Azure haven't yet developed state of the art kubernetes cloud service, no one except Google have, just don't claim you did if you want us to believe you when it labeled GA that we can use it for real workloads.

verst 8y ago
You are correct. The provisioning sucked. I will be fully transparent about that. In fact, I had the same problems myself. You can see the list of issues here [1]. That provisioning madness is actually unrelated to AKS, but it's being addressed by the team. This is one of the reasons why the service isn't GA yet. I'd say give it a try in the EastUS region, or some time after GA. Once you do have an AKS cluster up it all works well. [1]: https://github.com/Azure/AKS/issues https://github.com/Azure/AKS/issues

bboreham 8y ago

I’m sure it is immensely irritating to Google that they aren’t even second to AWS, but I’m pretty sure it was not Microsoft they were aiming at with Kubernetes. To me, it’s a re-run of the X Window System playbook, where Digital managed to break Sun and Apollo’s lock on workstation tools. Digital didn’t particularly win that one either.