I'm seeking advice on a Kubernetes scenario where I need to handle large full memory crash dumps (over 100GB) from a Windows pod running in Azure Kubernetes Service (AKS). Specifically, I want to ensure these dumps are captured reliably, saved without corruption, and are easily downloadable or inspectable later. I've experimented with using a premium Azure disk (az-disk) but it hasn't worked reliably for this task. I'm also considering options like emptyDir but haven't tried that yet. Any suggestions would be really helpful! Thanks!
2 Answers
It sounds like you're in a tough spot! I'd recommend flushing those dumps as soon as possible to handle them properly. And maybe look into refactoring your app if it's creating such huge memory dumps—there might be a way to optimize that.
What’s the main goal with these dumps? Are you debugging an application? Depending on your use case, it might help to know more about what app you're running in your Windows pod. I totally understand your frustration with Windows containers in Kubernetes; they can be a bit tricky!
Yeah, I’m just trying to debug the app. It's definitely a hassle working with Windows containers!