Diagnostic Tooling: How to get insights from your .NET services hosted in Kubernetes containers?

Cloud-native development is the talk of the town. Kubernetes, private cloud, and on-prem hosting are the hottest things around. However, running your services in containers on Kubernetes brings new challenges, especially if they are set up to be particularly secure in a production environment. Bugs exist in every software, but how can you obtain the data required for diagnostic purposes from services running in such containers? How can you obtain the data to analyze memory or performance patterns and do optimizations? In this talk, I will answer questions of this kind when dealing with .NET services hosted in a Kubernetes environment. I will explain concepts of .NET and reason about existing tools for getting memory dumps, heap information, CPU traces, etc., and what that means for your container setup. Key Takeaways: - Tooling and Integration: The available tools and their practical applications for .NET services running in Kubernetes. - Sidecar Configuration: Step-by-step guidance on setting up a diagnostic sidecar container in your Kubernetes environment. - Deployment Readiness: Recommendations for preparing your Kubernetes deployment manifests. - Debugging and Diagnostics: How to extract traces, dumps, heap data, and other diagnostics from .NET services in containers and export them for analysis. - .NET concepts: How to fetch diagnostic data from .NET services?