What are your main problems with AKS? I’m setting up a new greenfield project and have to use it. Would be nice to avoid done pitfalls.
back
2 comments
I second this. Seriously, don't use AKS. It looks so nice in the docs. In practice, you'll run into so many issues, I'm convinced no one actually uses AKS in production for anything major.
If your apps are simple enough that you can get away with Azure Container Instances/Apps, use them.
If you need proper managed k8, use OpenShift. Microsoft has a partnership with RedHat and RH provides full support.
Some examples of those issues would be nice to back up your claim.
Alright that’s pretty bad but also 5 years ago.
Literally 4 weeks ago we had to migrated over to another host because we couldn't create another node pool.
I don't think the age of the article matters.
Interesting, thanks!
At my employer teams are preparing to extensively use hybrid AKS. I'd really appreciate hearing any of the issues encountered.
Microsoft uses AKS for their production workloads, but only for “minor” projects like “Office 365” which only has a “few” (200 million) users.
https://customers.microsoft.com/en-us/story/1536483517282553...
What on God's green earth makes you think MS is going to release their dirty laundry to the public about one of their products using another one of their own products?
Like there's a litany of literature of how AKS completely dropped the ball, you don't have to take anyone's word on it from this thread. The difference between AKS and other offerings is _striking_.
They come in different shapes and sizes. Stability of the host environment is the main thing. Don't have to take my word for it: https://movingfulcrum.com/horrors-of-using-azure-kubernetes-...