I'm tackling a Kubernetes challenge and need some help. Specifically, how can I effectively capture and store very large full memory crash dumps (over 100GB) from a Windows pod in Azure Kubernetes Service (AKS) after it crashes? It's crucial that these dumps are saved without any corruption so I can download or inspect them later. To provide extra context, I've already tried using a premium Azure disk (az-disk), but that hasn't been reliable for this purpose. I'm also considering options like emptyDir but haven't tested them yet. Any suggestions or insights would be greatly appreciated!
1 Answer
I feel you on this one! It's a tricky situation with Windows pods, especially when dealing with such large dumps. Have you thought about tweaking your application's memory management? Sometimes refactoring could help reduce dump sizes. Just a thought! Also, out of curiosity, what's your ultimate goal here? Are you debugging a specific application?
I'm really just trying to debug the application. It's a Windows pod that unfortunately generates those massive memory dumps. Honestly, I really dislike working with Windows containers in Kubernetes; it's such a hassle!