2 ms·
>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 w
by 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 agoYou 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