<h1 id="tldr">TL;DR</h1>
First get a shell within the pod:
<pre><code>kubectl exec --stdin --tty &lt;Pod Name&gt; -n &lt;Pod Namespace&gt; -- cmd
</code></pre>then install procdump using choco:
<pre><code>C:\&gt; choco install procdump
</code></pre>find the running processes:
<pre><code>C:\&gt; powershell
PS C:\&gt; Get-Process
PS C:\&gt; exit
</code></pre>then run procdump:
<pre><code>C:\&gt; procdump -e 1 -f "" &lt;process id&gt;
</code></pre><h3 id="use-case">Use Case</h3>
So, I needed to find a way to debug an application (.NET) running on a Windows Pod. The app was running, but not working as expected, it was crashing before even App Insights was loaded - so I was pretty much blind on what was going on. On the good old days I would use <code>procdump</code> to log exceptions on my console <code>(procdump -e 1 -f "" w3wp.exe)</code> , but how to do such a thing when the app runs on Kubernetes?
Well, first I needed to get a shell within the pod / container (?), then install procdump (?), then get my process id (?), and finally running the procdump with the proper switches.
As it ends up, all of the above are just 4 commands away...

# TL;DR
First get a shell within the pod:

```
kubectl exec --stdin --tty <Pod Name> -n <Pod Namespace> -- cmd
``` 
then install procdump using choco:

```
C:\> choco install procdump
``` 
find the running processes:

```
C:\> powershell
PS C:\> Get-Process
PS C:\> exit
``` 

then run procdump:

```
C:\> procdump -e 1 -f "" <process id>
``` 
### Use Case
So, I needed to find a way to debug an application (.NET) running on a Windows Pod. The app was running, but not working as expected, it was crashing before even App Insights was loaded - so I was pretty much blind on what was going on. On the good old days I would use `procdump` to log exceptions on my console `(procdump -e 1 -f "" w3wp.exe)` , but how to do such a thing when the app runs on Kubernetes?
Well, first I needed to get a shell within the pod / container (?), then install procdump (?), then get my process id (?), and finally running the procdump with the proper switches.
As it ends up, all of the above are just 4 commands away...

How to run procdump within a Kubernetes Pod

Applies on Windows Node pools

TL;DR

Use Case