The lessons noted in the article, all valid, can easily be generalised applied to any infrastructure, not just Kubernetes.
Thanks :)
Readit Newsjonsson101 commented on Learnings from our years of Kubernetes in production medium.com/@.anders/learn... · Posted by u/jonsson101
jonsson101 commented on Learnings from our years of Kubernetes in production medium.com/@.anders/learn... · Posted by u/jonsson101
Thanks for clarification. On one hand I’m happy about you sharing this experience. On the other hand, I still feel we can’t assess the true value as it would require disclosing important information that you’d likely not be allowed to share.
Let me know what you're interested in learning more about, and I'll see what I can share. If you're looking to dive deeper into specific details, we could discuss them further in a video call or similar.
jonsson101 commented on Learnings from our years of Kubernetes in production medium.com/@.anders/learn... · Posted by u/jonsson101
Not a native English speaker, but when exactly did "lessons" get replaced by "learnings"?
To me the latter always sounds very unsophisticated.
Thanks for your feedback on the title of my article. English is not my first language, and in my native tongue, the distinction between “learnings” and “lessons” isn’t as pronounced in this type of context. I appreciate the nuanced perspective and will probably update my title . My main goal is to share the experiences we’ve gathered over the years, and I hope that the essence of our journey with Kubernetes shines through, regardless of the terminology.
jonsson101 commented on Learnings from our years of Kubernetes in production medium.com/@.anders/learn... · Posted by u/jonsson101
What I really miss in articles like this - and I understand why to some degree - what the actual numbers would be.
Admitting that you need at least two full-time engineers working on Kubernetes I wonder how that kind of investment pay’s itself back, especially because of all the added complexity.
I desperately would like to rebuild their environment on regular VMs, maybe not even containerized and understand what the infrastructure cost would have been. And what the maintenance burden would have been as compared to kubernetes.
Maybe it’s not about pure infrastructure cost but about the development-to-production pipeline. But still.
These is just so much context that seems relevant to understand if an investment in kubernetes is warranted or not.
Sorry for being unclear on this. In our case, we needed a couple of engineers who, in addition to their regular duties, would devote their time to Kubernetes as the go-to experts whenever necessary. Some weeks there was nothing to do; other weeks, particularly during cluster updates, they needed to focus exclusively on that work.
jonsson101 commented on Learnings from our years of Kubernetes in production medium.com/@.anders/learn... · Posted by u/jonsson101
Any documentation on this?
> This is very context-specific, but depending on the node type, AKS reserves about ~10-30% of the available memory (for internal AKS services)
Good point!
25% of the first 4GB of memory, 20% of the next 4GB of memory (up to 8GB), 10% of the next 8GB of memory (up to 16GB), 6% of the next 112GB of memory (up to 128GB), 2% of any memory above 128GB
"AKS reserves an additional 2GB for system process in Windows nodes that are not part of the calculated memory."
https://learn.microsoft.com/en-us/azure/aks/concepts-cluster...