jonsson101

Thanks :)

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.

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.

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.

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...